Our journal entry approval workflow has been stuck at the manager approval step for over four days now. Multiple entries are affected - about 15 documents totaling significant amounts that need to be posted before month-end close. The strange part is there are absolutely no error messages visible in the user interface when managers try to access the approval tasks. The workflow was working fine until last week. Managers can see the work items in their inbox (transaction SBWP), but when they click to approve, nothing happens. We’ve tried having different managers attempt the approval, but the same issue occurs. As a temporary workaround, we’ve been manually restarting the workflow for each entry, which then allows approval, but this isn’t sustainable. We need entries to proceed to the next approval level automatically as designed. Has anyone experienced workflow tasks getting stuck like this without any visible errors? Running SAP S/4HANA 1909.
Your issue stems from a workflow engine processing problem where tasks appear in user inboxes but cannot be executed. Here’s the systematic diagnosis and resolution:
Workflow Task Stuck at Manager Approval: The root cause is typically a disconnect between the workflow work item status and the actual business object status. Execute transaction SWIA (Workflow Diagnosis) and enter one of the affected work item IDs. Look specifically at the “Execution” section - if you see status “Ready” but the actual execution log shows no processing attempts, this confirms the workflow engine isn’t picking up the approval action.
Run transaction SWI2_DIAG for detailed analysis. Select “Work Items Without Agents” and “Work Items in Error” - even though no errors are visible in the UI, background processing errors often exist at the engine level. Document any work items found here.
No Error Messages in User Interface: This is characteristic of workflow buffer inconsistency. The workflow definition exists in memory differently than in the database. Execute these steps in sequence:
- Transaction SWU_OBUF - Clear workflow runtime object buffer
- Transaction SWPR - Refresh workflow event trace settings
- Transaction SBWP - Have managers refresh their inbox (F5) after buffer clear
If the issue persists, check transaction SWEL (Event Trace). Activate the trace temporarily, then have a manager attempt approval. Review the trace to see if the approval button click generates the expected workflow event. Missing events indicate a UI-to-workflow communication breakdown.
Entries Cannot Proceed Automatically: Verify your workflow step configuration in transaction SWDD. Open the manager approval step and check:
- Terminating events are properly defined
- Binding between approval outcome and workflow container is correct
- The subsequent step’s start conditions reference the correct container element
Common issue: If the workflow is waiting for a specific event (like APPROVED or REJECTED) but the approval action is generating a different event name, the workflow will never advance. Check table SWFREVTLOG to see what events are actually being triggered.
Manual Workflow Restart Workaround Analysis: The fact that manual restart works indicates the workflow definition itself is sound - the problem is with work item state management. Execute transaction SWI1 for a stuck work item and use “Restart After Error” function. Before restarting, note the current step name and container contents. Compare these with a work item that required manual restart - you’ll likely find the container is missing a critical element or has an incorrect status flag.
Comprehensive Resolution: Run transaction SWPR and execute “Automatic Workflow Customizing” to regenerate all workflow runtime structures. This often resolves mysterious stuck-task scenarios. Then execute report RSWUWFML2 (Consistency Check for Workflows) to identify and fix any workflow-to-organization management inconsistencies.
Finally, implement workflow error monitoring: Schedule report RSWWERRE daily to proactively identify stuck workflows before they impact operations. Set up email alerts for workflow administrators when work items exceed defined age thresholds using transaction SWETYPV event linkage to a custom notification workflow.
This draft is based on general SAP S/4HANA knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.
This sounds like a workflow runtime issue. Check transaction SWI1 to view the workflow log for one of the stuck work items. Look for any background errors that aren’t surfacing to the user interface. Also verify that the workflow definition hasn’t been changed recently - sometimes transport imports can corrupt workflow containers or agent assignments.
Check your workflow background jobs. Execute transaction SM37 and look for jobs starting with SWW*. If these jobs are failing or not scheduled correctly, work items won’t process properly even though they appear in user inboxes. The symptom you describe - work items visible but not actionable - often indicates that the workflow event queue isn’t being processed.
Checked SWI1 and found something interesting - the workflow log shows status “Started” but no completion timestamp. The background jobs in SM37 are running on schedule, but I see several SWWDHEX jobs completed with warnings. Could these warnings be related to our stuck approvals?
Yes, SWWDHEX warnings are definitely significant. This job processes deadline monitoring for workflows. If it’s completing with warnings, your workflow deadlines might not be triggering properly, which could cause tasks to remain in limbo. Check transaction SWETYPV to verify your event linkages are active. Also run transaction SWUE to check for any event queue backlogs that might be preventing the workflow from advancing to the next step.
I’d also recommend checking whether any workflow customizing was recently changed. Use transaction SWDD to open your journal entry workflow definition and verify that the agent determination for the manager approval step is still correctly configured. Sometimes organization management changes can break agent assignments without throwing obvious errors.
Look at transaction SWI2_FREQ to identify workflows with high error frequencies. This will help you spot patterns in the stuck work items. Also check if buffer synchronization is an issue - run transaction SWUS to refresh the workflow runtime buffers.