Platform
Task Run Observability
Observe automation templates and run history, trigger permitted operations, and retry eligible failures.
What this menu does
Provide a controlled operations view for background and scheduled automation without exposing configuration editing here.
Where to find it
Platform Admin navigation: Task Run Observability.
When to use it
- Review available operation templates.
- Filter run history by operation, status, trigger, or date.
- Trigger an allowed template.
- Retry an eligible failed run.
Before you begin
- Sign in to Platform Admin.
- The account must be allowed to view this menu.
Page regions
- 01Operation templates
- 02Trigger actions when allowed
- 03Run-history filters
- 04Run list and failure reason
- 05Retry action
- 06Toast feedback
Supported operations
Review run history
- 1
Review the available operation templates and their descriptions.
- 2
Filter history by operation, status, trigger type, and created date range.
- 3
Open or inspect the target run's status and business-safe failure reason.
- 4
Preserve the run or request identifier when escalating.
The run remains unchanged and its outcome is traceable.
Trigger an operation
- 1
Confirm the operation template and its business impact.
- 2
Select Trigger when the action is visible.
- 3
Wait for the success or failure toast.
- 4
Refresh or review run history to confirm the new run.
A new run appears in history if the trigger is accepted.
Retry a failed run
- 1
Review the failure code and business reason.
- 2
Correct the source condition outside this page when needed.
- 3
Select Retry on the eligible run.
- 4
Compare the new run outcome with the original.
Retry creates another controlled attempt; it does not erase the original failure history.
Business rules and fields
- The page shows operation templates and run history, not schedule configuration controls.
- Trigger and retry actions require their own business access.
- Retry only after understanding the failure; repeated retries can duplicate load without fixing the cause.
States you may see
What happens next
- Operations staff can observe and, when authorized, safely re-run supported automation.
Common problems
The menu or action is missing.
The account does not have the required platform access or the item is not available in the current state.
Ask a platform administrator to verify the account role and the record status.
A save or load action fails.
The session may have expired, validation may have failed, or the service is temporarily unavailable.
Keep the shown request identifier if present, refresh once, correct highlighted fields, and retry. Escalate with the request identifier if it repeats.