mailerpress/get-batch-chunks is a debug-oriented drill-down into a send batch’s chunks, which are the unit of Action Scheduler dispatch.
Use it when a batch stalls.
At a glance
| Ability | mailerpress/get-batch-chunks |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Campaigns & Sending |
| 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
A stalled send is the most common operational problem with MailerPress, and it is almost always Action Scheduler rather than MailerPress — a site whose scheduler is not running has chunks sitting pending forever.
The chunk states distinguish the cases: pending chunks with past scheduled times mean the scheduler is not running; processing chunks that never complete mean something is failing mid-dispatch.
The scheduled times are what make the first diagnosis possible. A chunk scheduled for two hours ago and still pending is not waiting its turn.
It is also how you answer “how much of this send has gone out” during a pause decision — completed chunks are delivered and cannot be recalled.
Debug-oriented rather than reporting-oriented: the engagement figures live at batch level.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
batch_id | integer | Yes | The send batch. |
What comes back
| Name | Type | What it is |
|---|---|---|
chunks | array | Each chunk with its state — pending, processing or completed — and scheduled time. |
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:
Why has this send stopped?
It resolves to one call:
{
"ability": "mailerpress/get-batch-chunks",
"parameters": {
"batch_id": 91
}
}Worth knowing
- A stalled send is usually Action Scheduler, not MailerPress.
- Pending chunks with past scheduled times are the signature of that.
- Completed chunks are delivered and cannot be recalled.
- Engagement figures are at batch level, not here.
Related abilities
- MailerPress Get Campaign Batches — the batch level
- MailerPress Pause Campaign Batch — stop the rest
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category