KNOWLEDGE BASE ARTICLE

Working with Umango and File Locking Errors

File locking in Umango is handled differently across 3 different locking scenarios:
  1. Source files (eg. watched folder): Umango will wait for the file to become available but eventually will timeout. If the wait time is exhausted then the file will be moved to the bottom of the processing queue and the system will try again when it reaches the top of the queue.
  2. Destination files targeted by jobs that can combine data/documents across processors: Umango locks processing threads across all processors and all jobs and only allows 1 processor to write to the destination files at a time. File writes are performed in the order the thread arrives at the file write request.
  3. Destination files locked by third part applications: If a file is locked (not by Umango's file combining process discussed in point 2 above) an export error will occur and the batch will be released for user intervention.

Cloud Syncing Services

In the passed we have observed file locking errors in folders that are cloud synced (eg. OneDrive, Dropbox etc). These cloud syncing services offer disc saving options where they only download files from their cloud copy when they are required. What we are referring to here is OneDrive's "Files On Demand" (more info) or Dropbox's "Smart Sync" (more info). Other providers have their own names for these features.

However, when Umango is watching a folder, or writing to a file with these rules in place, the file system may report the files as locked and Umango will treat them accordingly. We would strongly recommend that, with any folders Umango is watching and any folders Umango will be exporting to and combining files (eg. appended CSV's), these folders should be set to keep a copy on the physical device or not included in cloud syncing at all.

Link to this article http://umango.com/KB?article=118

Related Tags

sync onedrive dropbox lock
© Umango PTY LTD - An i2 Software Company
Powered by HTML5