Hi there,

One of our clients encountered an issue recently where in one tab they were uploading a batch of large files that was taking a very long time. While this was happening, they had another tab open so they could do other Laserfiche work in the meantime. This involved changing metadata on an entry to trigger a workflow to move the entry. Before they initiated the file upload in the other tab, this was working fine. However, once the file upload started, the files were no longer moving as expected and they contacted us. When I took a look, the workflow wasn't even being triggered during this time. I asked them to wait until the file upload was finished to see if perhaps it was just "queued" but they never did run. The client had to change the metadata back to the original value, save, and change it to the new value and then the workflow was triggered as expected, with no change to the starting rule/workflow itself. The only difference - it would seem - between running and not running was the large file upload.

Has anyone encountered something similar before in Laserfiche Cloud? While this user was knowledgeable enough and the process was simple enough that it was obvious it did not run and they knew how to manually trigger it, my concern would be for other users/processes that it's not as obvious that it did not run and they might not know how to trigger or could not easily trigger the process after knowing it did not run.

Thanks for any input/insight!