Pausing, Resuming and Stopping a Run
Who may pause, resume or stop, what happens to the records in progress, the pause reasons and their next steps, and which runs resume by themselves.
Draft brief for authors. Replace with the final text; keep the task-page structure. Include the pause reasons table.
Page type: Task · Audience: Processor (Editor for uploads)
Contains
- Pause / Resume / Stop under Background Jobs; Stop also from the Monitor's Action menu (every run of a Task).
- Records in progress finish; the rest stay Not Started; a resume continues the same run.
- Pause reasons and next steps: User · SAP system not responding (resume once SAP answers) · Connection to SAP not usable (fix the cause, then resume) · Interrupted (integration-user runs resume by themselves within minutes) · Interrupted, named user (sign in and resume) · Sign-in expired (sign in and resume) · Add-on quota used up (ask for an extension, then resume).
- A named-user run resumes as the person who resumes it, checked with SAP first.
- An immediate run can be stopped but not paused.
Related information: app-background-jobs, messages-processing, managing-add-ons-and-quota.
Source in the product repository: .claude/rules/mass-processing.md (D41, D46), customer guide §8.
Last updated: