Workflow · Workflow Stuck Explainer
Work item READY without any possible agent
- Default severity
- Critical
- Finding code:
- WF_STUCK_NO_AGENT
- Engine version:
- 2.1.0
What this finding means
Workflow Stuck Explainer reports this finding with the default severity “Critical”.
About the engine: SWWWIHEAD / SWZAI analysis for blocked work items
How to fix it
Forward the work item in SWIA; then fix the agent rule (PFAC / 'Manage Workflows' responsibility rules) and the org assignment (PPOME) so it resolves to at least one active user.
How ERP Preflight detects it
The analysis is deterministic: the same exported files and the same knowledge snapshot always produce the same findings. No SAP system connection is required — you upload exports.
- Engine
- Workflow Stuck Explainer
- Accepted formats
- JSON, CSV
- What to export
Workflow runtime extracts: JSON {'swwwihead': [{wi_id, wi_type, wi_stat, wi_rh_task}], 'swwloghist': [...], 'agent_traces': [...], 'swetypv': [...], 'containers': [...], 'deadlines': [...]} or CSV exports of SWWWIHEAD / SWWLOGHIST / SWETYPV with their column headers.
- Required input
- SWWWIHEAD work items (or other workflow runtime tables)
- Evidence
- Each finding points to the artifact path, line and column, the code snippet and the SHA-256 of the uploaded file. Findings without such a pointer are demoted to confidence UNKNOWN.
- Confidence
- The verdict rests on your artifacts only. Each finding carries a confidence class (VERIFIED, RULE_DERIVED, INFERRED or UNKNOWN) that shows how strong the evidence is.
- Target releases of the engine
- S4H_2022, S4H_2023, S4HANA_CLOUD_2402, S4HANA_CLOUD_2408
Related findings
- BlockerCircular wait between work items
- CriticalBackground step ended in error
- MajorContainer element empty or binding failed
- MajorDeadline / SLA exceeded
- MajorEvent type linkage deactivated
Terms used on this page
Background reading
- Why SAP Business Workflow items get stuck and how to find the causeThe typical reasons a workflow does not continue — no agent found, failed background steps, missing events, configuration gaps — and the standard tools to diagnose them.