Operations
Daily operations
Section titled “Daily operations”- Logs and CSV export
- Queue retry and dead-letter inspection
- Scheduled email and cancellation
- Large attachments stored in customer R2
- Runtime health and release diagnostics
- Staged upgrades and rollback evidence
Runtime continuity
Section titled “Runtime continuity”A deployed Runtime keeps sending when the CFsend console is unavailable or Cloudflare is disconnected. Deployment, managed upgrade and repair actions require the CFsend control plane.
Free customers operate their own deployed Runtime. Pro adds managed verification, upgrades and rollback; Business adds staged fleet operations.
Routine checks
Section titled “Routine checks”Review Runtime health/version, failed queue work, bounce/complaint changes, domain drift and recent webhook failures. Confirm scheduled and Automation work is advancing. Use retention and export settings appropriate to your data policy; attachments remain in customer R2.
Safe changes
Section titled “Safe changes”Before an upgrade, record current Runtime version and verification result. A managed update must pass compatibility and smoke gates before it becomes the healthy version. Keep rollback evidence and do not change D1/R2/Queue bindings during the operation. Free can continue operating its installed Runtime without managed upgrades.
Incident sequence
Section titled “Incident sequence”First preserve the last healthy Runtime and evidence. Identify whether failure occurs before acceptance, in Queue/provider delivery, or after delivery in event processing. Restore the failed dependency, run Verify, send one idempotent controlled test, and only then resume volume. The control plane is required for install/managed repair, not for ordinary calls to an existing Runtime.