Entry processing & batching
Every flow entry submitted through the API receives a processing state. Pending entries wait for the next run, batched entries were included in a mailing, skipped entries were intentionally skipped, failed entries could not be processed and removed entries are ones you removed from the planned mailing yourself. This batching turns ongoing individual events into printable mailings.
API flows turn ongoing individual events into printable batches. To do that, each flow entry receives a state.
States:
- pending - waiting for processing.
- batched - included in a mailing.
- skipped - intentionally skipped.
- failed - could not be processed.
- Removed - removed by you from the planned mailing.
During the next trigger window, PostPal collects matching pending entries and creates a mailing batch from them.
In the API logs, Mailing Status shows how far the assignment has progressed: Not Started means no mailing yet, In Progress means the mailing is being created, Done means it has been commissioned for printing, and Excluded means the request is not included in the mailing.
Removing and restoring requests: in the API logs you can take single or multiple requests out of a mailing that has not been created yet. They receive the Removed label, are neither printed nor sent, and stay visible as a log entry. This only works for pending entries — anything already batched belongs to a created mailing and stays unchanged.
Restoring moves a removed entry back into processing. It only works while the trigger
window is open: once the mailing has been created or the related API flow has
been deleted, the request can no longer be taken back in. Re-sending the same
request is not a substitute — PostPal recognises it as a duplicate and answers
with 409.
A third bound is the retention period: 60 days after the request arrived, its recipient data in the log is anonymized. An entry still removed at that point can no longer be restored — without a name and address there would be nothing left to print. If you may still want to send a removed request later, restore it before the period ends, or submit it as a new request with a new request ID.
If you remove enough requests to drop below the flow's threshold, the mailing moves to the next window in which the threshold is met again. The confirmation dialog points this out.
Frequently asked questions
What does pending mean?
The entry was accepted and is waiting for the next matching flow run.
What does batched mean?
The entry was included in a mailing batch.
What happens when an entry is failed?
The entry could not be processed. Use API logs and the flow view to investigate the cause.
What does Removed mean?
You removed this request from the planned mailing in the API logs. It will not be printed or sent, but stays visible as a log entry. The API logs guide explains how.
Can I put a removed request back?
As long as the trigger window is still open, yes — the entry becomes pending again. Once the mailing has been created, the related API flow has been deleted, or the 60-day retention period has passed, it is no longer possible. After the retention period the recipient data is anonymized and cannot be recovered; only a new request with a new request ID helps there. Re-sending the same request does not help in any of these cases: PostPal recognises it as a duplicate and answers with 409.