A custom Event configured on a table fires correctly when a record is created/updated interactively, but doesn't trigger its linked workflow when the same insert/update happens via a scheduled Database Task (background job) instead. Why?

All FAQ questions / Workflows and automation

Answer

Check the workflow's trigger timing setting — Asynchronous is the only timing option that actually works for a workflow being triggered from a background/scheduled job context; if it's set to a synchronous timing (which assumes an interactive client session), it silently won't fire from a Database Task's batch execution.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Workflows and automation questions