Error to start recording, but jibri goes BUSY and start the recording

When I scaled Jibri servers with aws autoscaling based on jibri status.
Jibri scaled and start recording but on jitsi web getting recorders are busy error. This is happening only when Jibri server scaled and for first recording.

I
jicofo.log (31.6 KB)
jvb.log (72.1 KB)
log.0.txt (5.5 KB)
can see the ffmpeg started the recording in recording location.