Automation
Automation jobs & logs
Inspect automation jobs, worker logs, queue state, and failed run diagnostics.
Automation jobs & logs
Automation jobs & logs covers run history, queued jobs, node logs, errors, retries, and audit evidence for automations and workflows. Use this page when you are setting up the product surface, reviewing a rollout, or troubleshooting why users see a different result from an administrator.
What this surface is
- Primary purpose: run history, queued jobs, node logs, errors, retries, and audit evidence for automations and workflows.
- Where users start: Workflow lists live at
/automation/automations/list; playground is at/automation/playground. - Where administrators configure it: Tenant logs are at
/settings/application/tenant-logs; workflow run details and job logs are reached from automation debug surfaces. - Runtime/detail surface: Logs show which trigger fired, what data entered the workflow, which nodes ran, and where a failure occurred.
- Platform connections: Jobs and logs connect triggers, scripts, webhooks, workflow versions, node names, side effects, and usage metering.
Where it lives
| Area | Path or surface | Use it for |
|---|---|---|
| User surface | Workflow lists live at /automation/automations/list; playground is at /automation/playground. | Day-to-day work and review. |
| Configuration | Tenant logs are at /settings/application/tenant-logs; workflow run details and job logs are reached from automation debug surfaces. | Setup, permissions, routing, labels, and behaviour. |
| Runtime/detail | Logs show which trigger fired, what data entered the workflow, which nodes ran, and where a failure occurred. | Testing the live experience users actually see. |
Configure it
- Confirm the audience for this surface and whether they are staff users, portal users, customers, public visitors, or administrators.
- Open the owning product route: Workflow lists live at
/automation/automations/list; playground is at/automation/playground. - Review the configuration route and permissions before changing live behaviour: Tenant logs are at
/settings/application/tenant-logs; workflow run details and job logs are reached from automation debug surfaces. - Define the primary records, fields, statuses, owners, and notifications involved in this workflow.
- Configure Queued job, Successful run, and Failed run first because they shape the rest of the rollout.
- Add Skipped branch and Script error only after the core path works with sample data.
- Test the runtime surface as a restricted user, not only as a superadmin: Logs show which trigger fired, what data entered the workflow, which nodes ran, and where a failure occurred.
- Check downstream connections after saving: Jobs and logs connect triggers, scripts, webhooks, workflow versions, node names, side effects, and usage metering.
- Record the owner, rollout date, and support path for the configuration.
- Review the first week of activity and remove any option that users do not understand or need.
Configuration options
| Option | Use when | Notes |
|---|---|---|
| Queued job | Work has not started yet | Check queue pressure and trigger timing. |
| Successful run | Audit or confirmation is needed | Confirm expected side effects occurred. |
| Failed run | A node, script, webhook, or permission failed | Read the first error. |
| Skipped branch | A decision did not match | Check condition data and field values. |
| Script error | Custom code failed | Use script logs and playground. |
| Webhook error | External endpoint failed | Check request/response logs and retry policy. |
Operating notes
- Keep labels aligned with the words users see in the product, especially Queued job and Successful run.
- Permissions still matter even when a menu, page, or link is visible.
- If users see empty data, check role filters, enabled apps, ownership rules, and saved filters before editing records.
- If a change affects customers or public visitors, test from a logged-out or customer account as appropriate.
- Use reports or logs to confirm the change produced the expected operational result.
- Capture configuration decisions in rollout notes so support teams know what changed.
- Do not reuse one option for unrelated processes just because it is already configured.
- Review linked notifications, workflows, dashboards, and reports after changing this surface.
- Prefer narrow changes that can be tested with sample data before a tenant-wide rollout.
- When troubleshooting, start at the route users open, then inspect configuration, permissions, and logs in that order.
- Keep retired settings hidden or archived so users do not choose outdated paths.
- Assign an owner for ongoing review; unattended configuration becomes stale quickly.
For developers
Use these pages when the surface is read or changed by code, scripts, embeds, widgets, API clients, webhooks, or realtime listeners.
- /developer/scripts-api
- /developer/outbound-webhooks
- /developer/inbound-webhooks
- /reference/side-effects