Skip to main content

FME Workspace Scheduler allows you to skip a job if it's already in progress. However, if you have a workbench that is triggered by both a schedule and an automation then the same workbench could potentially run at the same time (one on an engine and one on a dynamic engine). In general, I'd like to be able to have a setting at the workbench level that ensures that the workbench itself will never be run simultaneously. Right now we have an automation that redirects workbenches to dynamic engines but it's resulting in db locks and other issues.

This is related to https://community.safe.com/ideas/skip-automation-trigger-if-it-is-already-running-32846