Background tasks also need visibility; leaving the current screen does not make the task disappear

What it is

Exports, synchronization, publication, batch jobs, and message sending often continue after users navigate away, minimize, or close a tab. Background task visibility requires a cross-page or cross-session task center, global indicator, or notification—not a state trapped in the original dialog.

Why it happens

When runtime exceeds time on a screen, status must bind to the task object rather than the view component. Leaving the page should neither cancel nor hide the task; on return, users need progress, failure reason, result file, or affected records. Without a global entry, they resubmit, assume failure, or cannot resolve a partially completed state.

Where it stops holding

Visibility does not mean every background activity should interrupt. Brief synchronization can use a small status dot; consequential batch jobs belong in a task center. System sleep, permissions, mobile background limits, and browser closure may interrupt work. The interface must distinguish “running,” “paused,” “failed/retry,” and “partially complete,” not disguise platform limits as continued activity.

Applying it

• Give long tasks a unique task ID recording status, stage, initiator, scope, result, and errors.
• Provide a global task entry with badge, progress return, result download, retry, and cancellation.
• Before users leave with a consequential unfinished task, say whether it will continue or stop and how to return to it.
• Test navigation away, refresh, re-login, offline, and multiple sessions to ensure consistent status without duplicate execution.

Related

• Same group: B3.01.1 Users should always know what the system is doing · B3.01.2 Status feedback must appear within a reasonable time · B3.01.3 Long tasks need progress rather than only a busy indicator · B3.01.4 The test is whether users can always answer what the system is doing and where they are · B3.01.5 After waiting long enough, feedback must upgrade from a momentary cue to a persistent status presentation · B3.01.7 Status should express progress and remaining work, not merely that the system is busy
• Nearby: H3 Cross-page Workflows · I1 State, Time, and Response
• Search terms: background job · task center · cross-page state