Platform
Background Jobs and Scheduling
How remoteEaze completes long-running work after a user action.
Last updated
Some actions in remoteEaze are intentionally completed in the background. This keeps the product responsive while still enforcing business controls.
What runs in the background
Background processing is used for work such as:
- notification fan-out
- import processing and review-stage commits
- export file generation
- upload validation and cleanup
- third-party delivery attempts and retries
- Close of Business orchestration
- scheduled scans and housekeeping tasks
What users should expect
When background work starts, users usually see a submitted or pending state first, then a final result after processing finishes.
The final outcome is visible in the relevant area, for example:
- export jobs in the exports area
- delivery logs in the third-party delivery area
- run and step status in Close of Business
- notification records in the notification inbox
Retry and failure behavior
Temporary infrastructure issues can be retried automatically.
Business-rule or configuration problems are treated as final failures and require user correction. In those cases, the system keeps the failure state visible so teams can act without guessing what happened.