Diagnose execution and operation issues with logs
Identify time, object, account, and task before choosing evidence.
Choose logs
| Purpose | Log | Entry |
|---|---|---|
| Task failure | Execution log | Scheduling history > Log |
| Backend failure | Service log | Log Management where provided |
| Business audit | Operation log | Log Management where provided |
Deployments may provide separate operational tools. Task logs do not replace full service/audit logs; check permissions/entry points.
Query service logs
- Filter service, level, and time.
- View full records.
- Copy contextual errors or export for analysis.
- Correlate business/task times.
Retain context beyond the final error and mask credentials, connections, and business data before sharing.
Query operation logs
Filter description, user, module, action, and time. Compare objects/history. Operation records do not prove approval or task success.
Provide operations with
- Entry, object, time, expected result.
- Actual message, task state, failure scope.
- Relevant execution/log evidence.
- Preceding connection, permission, rule, or schedule changes.
Related: Scheduling, Connections.