mailerpress/retry-import-batch re-queues the failed chunks of an import batch for another attempt.
Successful chunks are untouched, so nothing is imported twice.
At a glance
| Ability | mailerpress/retry-import-batch |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Contacts |
| 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
That selectivity is what makes retrying safe. A whole-batch retry would re-import the rows that succeeded, producing duplicates or a wall of duplicate-email errors.
Failed chunks are usually validation errors on individual contact rows — a malformed address, a required field missing, a value that does not match its field type.
Which means a plain retry often fails identically. The data is what is wrong, and retrying without fixing it changes nothing.
The retry is useful for the other case: a chunk that failed for a transient reason, such as a timeout or a temporary database problem, where the same rows will import fine on a second attempt.
mailerpress/track-import-progress is where the failed chunks are identified, and is worth reading to see whether the failures look like data or like infrastructure.
Not idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
batch_id | integer | Yes | The import batch. |
What comes back
| Name | Type | What it is |
|---|---|---|
requeued | integer | How many chunks 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 part of that import.
It resolves to one call:
{
"ability": "mailerpress/retry-import-batch",
"parameters": {
"batch_id": 12
}
}Worth knowing
- Only failed chunks are retried, so nothing is imported twice.
- Validation failures fail identically on retry — fix the data.
- Transient failures are what retrying is for.
- Not idempotent.
Related abilities
- MailerPress Track Import Progress — identify the failures
- MailerPress Import Contacts — the original import
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category