Swarm Daily: The Agent Loop Is Hitting the Guardrail

Supabase's recursive-call limit, Cloudflare's agent/workflow split, and Vercel's 7-day queue TTL show platforms now expect long-running AI work to move through explicit queues, retries, and time budgets.

The Big Thing

The notable shift is that recursive agent self-calls are being treated as an infra hazard, while queues and workflow engines are being promoted as the sanctioned place for retries, delays, fan-out, and human approvals.

Why it matters: the old move was to keep chaining functions, agents, or tools inside the same request thread until the work was done. Platform vendors are drawing a harder line. Real-time agent state can stay interactive, but long-running work now needs backlog semantics, step budgets, and idempotent scheduling. If your architecture still relies on ad hoc self-calls, you are operating against the direction of the platforms.

Supabase added a hosted-platform limit on recursive and nested Edge Function calls after internal recursion caused regional latency and an incident, which is a clear sign that function-to-function chatter is now being treated as shared-infra risk. https://supabase.com/changelog
Supabase's follow-up guide says the quiet part out loud: batch work, cap recursion depth, use queues for large workloads, and move shared logic into libraries instead of making more internal HTTP calls. https://supabase.com/docs/guides/functions/recursive-functions
Cloudflare's Agents SDK now pairs agents with Workflows explicitly: agents handle real-time communication and state, while Workflows handle long-running tasks, retries, and human-in-the-loop execution. https://developers.cloudflare.com/changelog/2026-02-03-agents-workflows-integration/
Cloudflare raised Workflows to as many as 25,000 steps per instance and framed it as support for more complex execution without recursive or child workflow calls, which is the same platform opinion expressed another way. https://developers.cloudflare.com/changelog/post/2026-03-03-step-limits-to-25k/
Vercel extended Queue message TTL to seven days, making delayed background work a first-class primitive instead of something you fake with request recursion or brittle cron glue. https://vercel.com/changelog/queues-now-supports-7-day-ttl

Code & Tools

Supabase Recursive / Nested Function Calls - the practical guide for handling recursive-call budgets with batching, depth limits, backoff, and queue handoff patterns. https://supabase.com/docs/guides/functions/recursive-functions
Cloudflare AgentWorkflow - the typed bridge for keeping live agent state separate from durable retries, sleeps, and human approvals. https://developers.cloudflare.com/changelog/2026-02-03-agents-workflows-integration/
Cloudflare Workflows limits - explicit budgets for step count, subrequests, queue depth, retention, and up to 365-day sleeps. https://developers.cloudflare.com/workflows/reference/limits/
Cloudflare idempotent schedule() - deduplicates schedule rows across Durable Object restarts so background loops do not silently multiply. https://developers.cloudflare.com/changelog/post/2026-03-23-agents-sdk-v080/
Vercel Queues - durable at-least-once delivery for background work, now with seven-day message TTL for delayed execution windows. https://vercel.com/changelog/queues-now-supports-7-day-ttl https://vercel.com/docs/queues/concepts

Tech Impact

Agent orchestration will keep moving from nested RPC trees to backlog-based designs. Queues and workflows give platforms room to meter retries, absorb spikes, and keep one bad loop from becoming everybody's outage. https://supabase.com/changelog https://vercel.com/docs/queues/concepts
Operators will need to budget steps, subrequests, queue depth, and retry windows just like they already budget tokens and CPU. Long-running automation is turning into an infra planning problem, not just a prompt-design problem. https://developers.cloudflare.com/workflows/reference/limits/ https://developers.cloudflare.com/changelog/post/2026-03-03-step-limits-to-25k/
Platforms will differentiate on safe background execution and deduped scheduling. The winning stacks will be the ones that can survive duplicate delivery, restarts, and delayed completion without inventing custom glue. https://developers.cloudflare.com/changelog/post/2026-03-23-agents-sdk-v080/ https://vercel.com/changelog/queues-now-supports-7-day-ttl

Meme of the Day

"Flowchart" (xkcd) - because every system that starts as "just call the next thing" eventually grows a loop arrow and a note that says do not let this recurse forever.

Image URL: https://imgs.xkcd.com/comics/flowchart.png
Post: https://xkcd.com/1195/