Read this if you use the File Watcher plugin

[Mike.Sheen]

This applies to not just our File Watcher plugin, but any plugin performing database operations which are invoked from another thread.

There is a risk database operations will error with "The transaction operation cannot be performed because there are pending requests working on this transaction".

Any database operation using our objects will get the above error if they, or any other plugin perform queries from another thread. The File Watcher plugin WILL be invoked from another thread, as at the plugin setup it hooks into the file system to receive notifications of when a file appears in a folder. When a file does appear, it is invoked from a thread outside the plugin scheduler thread.

If another plugin run on a schedule (or even another file watcher) has already started a SQL transaction (ie: performed a query and has not committed or rolled back yet), it potentially will be interrupted by the file watcher code - running on another thread - and that will cause the issue.

We've created an article on how to mitigate this: Plugin Scheduler Logs the error The transaction operation cannot be performed because there are pending requests working on this transaction.

We've also have a more elegant solution queued up for the next build in DEV-6017.