Why SAP Business Workflow items get stuck and how to find the cause

How a workflow moves forward

An SAP Business Workflow instance consists of steps. Each step creates a work item. Dialog work items wait for an agent to execute them; background work items are executed by the system; wait steps wait for an event. A workflow is "stuck" when one of these items can no longer progress.

Typical causes

• No agent determined. The agent rule returns nobody, or the possible agents of the task do not include the determined users. The work item is then in nobody's inbox.
• Error in a background step. A method raised an exception; the work item is in status Error and needs a restart after the cause is fixed.
• Missing event. A wait step expects an event that is never raised, for example because event linkage is inactive or the triggering application does not raise it.
• Incomplete runtime configuration. Basic workflow customizing, the background user or the event queue is not set up consistently in the system.

Standard diagnostics

• Workflow log of the instance: which step is active and in which status.
• Administration reports for work items with errors and for work items without agents.
• Diagnosis of the workflow runtime configuration and the event trace for missing events.
• Agent assignment of the task compared with the result of the agent rule.

Prevention

Test agent rules with realistic organisational data, monitor work items in error status, and keep event linkages and workflow customizing aligned across the landscape.

ERP Preflight's Workflow Stuck Explainer analyses exported work item and configuration data and explains the blocking cause with evidence. See Operations.