Overview
PulseGrid records every matching endpoint delivery separately.
Statuses:
- Pending: created and waiting for its first attempt.
- Processing: a worker has claimed the delivery.
- Retrying: the last attempt failed and another attempt is scheduled.
- Succeeded: the receiver returned an HTTP status from 200 through 299.
- Failed: all allowed attempts were used without a successful response.
- Cancelled: delivery stopped because the endpoint was paused or unavailable for processing.
The attempt allowance is controlled by the customer's plan and capped by the platform-wide safety setting.
Setup
Receiver response guidance:
- 200 OK: processed successfully.
- 202 Accepted: safely queued for later processing.
- 204 No Content: accepted successfully with no response body.
- 400 Bad Request: payload cannot be processed; PulseGrid may still retry until exhausted.
- 401 Unauthorized: signature or authentication rejected.
- 404 Not Found: receiver route is wrong or missing.
- 429 Too Many Requests: receiver is overloaded; PulseGrid retries according to its schedule.
- 500-599: temporary receiver failure; PulseGrid retries.
Keep the receiver fast. Avoid waiting for slow email, AI, SMS or third-party API work before responding.
Code example
HTTP/1.1 200 OK
Content-Type: application/json
{
"received": true
}Notes
The Recent activity row may show 1/5 attempts HTTP 200. This means the delivery succeeded on its first request and was allowed at most five attempts.
If a failed delivery is safe to try again, an authorised project member can use the Retry action. The receiving application must still enforce idempotency.