Symptom
Data Workbench executions remain in status "Stop Pending" for an extended period after manually stopping the job.
Environment
SAP Cloud for Customer
Reproducing the Issue
- Log in to the C4C system.
- Navigate to Data Workbench and open the Monitor view.
- Trigger an export for Account Address data.
- Start multiple export jobs in parallel.
- Monitor the executions and observe the increased processing time.
- Manually stop one of the running jobs.
- Observe that the task remains in status "Stop Pending".
Cause
The “Stop Pending” status indicates a controlled termination after a manual stop; the system completes the current processing step to ensure data consistency before fully stopping.
Multiple Data Workbench executions initiated in parallel create a processing queue, which increases both execution and stop times.
Resolution
This is expected behavior. When a DWB execution is manually stopped, the system completes the current processing step before terminating, keeping the status as "Stop Pending".
No action is required, as the status will automatically change once processing is finished. To avoid issues with large exports, split the data into multiple tasks and keep each batch below approximately 500,000 records.
See Also
Keywords
DWB; Data Workbench; Stop Pending; C4C; SAP Cloud for Customer; Parallel Execution; Job Queue; Mass Data Processing; Performance; Long Running Jobs; Execution Delay; Manual Stop; Graceful Shutdown; Batch Processing; High Data Volume; Throughput; System Processing; Monitor View; Export Job; Account Address , KBA , LOD-CRM-INT-DWB , Data Workbench , Problem
SAP Knowledge Base Article - Public