mailerpress/retry-failed-workflow-jobs retries FAILED jobs for a workflow. Provide a job_id to retry one, or omit it to retry every failed job for that workflow.
Only jobs in FAILED status can be retried; anything else returns invalid_status.
At a glance
| Ability | mailerpress/retry-failed-workflow-jobs |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Workflows |
| Requires | AcrossAI Pro, plus MailerPress active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Not idempotent — each call changes the row set, so re-running is not a no-op |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
A retried job resumes the contact’s progress through the workflow from where it failed, which means the actions before the failure do not repeat.
That matters: retrying a job that failed after sending an email does not send it again.
Whether a retry succeeds depends entirely on why it failed. A transient problem — a mail provider timeout, a database hiccup — retries cleanly. A configuration problem, such as a step referencing a deleted template, fails identically every time.
So reading mailerpress/get-workflow-logs first is what distinguishes a worth retrying from a fix-first.
Retrying everything for a workflow with a systematic fault is a loop: every job fails again, in the same place, for the same reason.
Not idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
id | integer | Yes | The workflow. |
job_id | integer | No | One job. Omit to retry every failed job. |
What comes back
| Name | Type | What it is |
|---|---|---|
retried | integer | How many jobs were re-queued. |
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:
Retry the failed jobs on that automation.
It resolves to one call:
{
"ability": "mailerpress/retry-failed-workflow-jobs",
"parameters": {
"id": 21
}
}Worth knowing
- A retry resumes from the failure point — earlier actions do not repeat.
- Transient failures retry cleanly; configuration failures do not.
- Retrying everything on a systematic fault just fails everything again.
- Not idempotent.
Related abilities
- MailerPress Get Workflow Logs — find out why they failed
- MailerPress Update Workflow Step — fix the step first
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category