FAQ

What happens if my endpoint is down?

Zeplo retries failed requests automatically based on the max_attempts setting (default: 3). Retries use exponential backoff. If all attempts fail, the request is marked as failed and you can be notified via webhooks or email.

Can I cancel a pending request?

Yes. If a request is still in pending or scheduled status, you can cancel it from the dashboard. Requests that are already processing cannot be cancelled.

What’s the difference between standard and FIFO queues?

Standard queues offer maximum throughput — requests are processed as quickly as possible, but order is not guaranteed. FIFO queues guarantee that requests are processed in the exact order they were enqueued, which is important for workflows where sequence matters.

How do I know if a request succeeded?

Check the request status in the dashboard, or configure webhooks to get notified on request.complete and request.fail events. The API also lets you query request status programmatically.

Is there a maximum delay?

Yes, you can delay a request up to 30 days (2,592,000 seconds).

Can I use Zeplo with serverless functions?

Absolutely. Zeplo works great with Vercel, AWS Lambda, Cloudflare Workers, and any platform that exposes HTTP endpoints. Just enqueue a request pointing to your function’s URL.

What if my request body is very large?

Bodies up to 256KB are handled inline. Larger payloads are automatically offloaded to cloud storage — this is transparent and requires no changes on your end.

How do I handle multiple environments?

See Environments for recommended patterns. The simplest approach is separate workspaces for dev/staging/prod.

Can multiple team members access the same workspace?

Yes. Workspaces support multiple members with role-based access (admin, member, viewer). Invite team members from Settings → Team in the dashboard.