MuleSoft · File Connector
FILE:FILE_LOCK
Short answer
FILE:FILE_LOCK means File Connector tried to lock a file and could not. Another process or flow is holding the file, so release that lock or read without locking.
VerifiedLast verified
01Error text
Error type: FILE:FILE_LOCK02Likely causes
- An attempt to lock a file was unsuccessful.
- The Read operation has Lock set to
true, and the file is already locked. A lock is held until the returned stream is closed or fully consumed.
03How to fix it
- Find what else has the file open, including other flows that read it with a lock.
- Make sure flows that lock the file consume or close the stream, so the lock is released.
- If locking is not needed, leave Lock at its default of
falseon the Read operation. - Handle the failure with an error handler of type
FILE:FILE_LOCKand retry later.
04Official documentation
→Related errors
- FILE:ACCESS_DENIEDFILE:ACCESS_DENIED means a File Connector operation tried an action on a file or path that the user running the app is not permitted to perform. Grant that user the permission on the path.
- FILE:ILLEGAL_PATHFILE:ILLEGAL_PATH means a File Connector operation was given a path that does not exist while Create parent directories is set to false. Correct the path, or let the operation create the missing directories.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer