mailerpress/list-failed-workflow-jobs returns a global list of failed workflow jobs across every workflow.
It is capped at five hundred rows by MailerPress, with no pagination.
At a glance
| Ability | mailerpress/list-failed-workflow-jobs |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Workflows |
| Requires | AcrossAI Pro, plus MailerPress active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
The cap is a hard one. A site with more than five hundred failures gets the first five hundred and no indication that more exist, so interval — the window in days — is the only way to see a complete picture on a busy site.
The endpoint accepts no per-workflow filter. Callers that need one must post-filter the returned array on automation_id themselves, which this page states rather than pretending the capability exists.
For one workflow specifically, mailerpress/get-workflow-logs is the paginated per-workflow read and is the better call.
The value of the global view is pattern-spotting: failures concentrated in one workflow point at that workflow, and failures spread across all of them at the same time point at something shared — a mail provider outage, a scheduler problem.
Remember that exits are normalised to failures in MailerPress’s own display, though this endpoint reports genuinely failed jobs.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
interval | integer | No | Window in days. The only way to narrow the result. |
What comes back
| Name | Type | What it is |
|---|---|---|
failed_jobs | array | Failed jobs across every workflow, capped at 500. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
Are any automations failing?
It resolves to one call:
{
"ability": "mailerpress/list-failed-workflow-jobs",
"parameters": {
"interval": 7
}
}Worth knowing
- Hard cap of 500 with no indication that more exist.
- No per-workflow filter — post-filter on
automation_idyourself. - The per-workflow log is the better call for one workflow.
- Failures spread across everything point at something shared.
Related abilities
- MailerPress Get Workflow Logs — one workflow, paginated
- MailerPress Retry Failed Workflow Jobs — retry them
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category