{"slug": "error-5408-is-a-design-review-check-the-limit-before-you-send-it", "title": "Error 5408 is a design review: check the limit before you send it", "summary": "A developer argues that United's ban on AI agents booking, changing or servicing tickets exposes a broader agent-design flaw: enforcement happens after the work is done, so bookings are confirmed and then silently canceled. Drawing on Cloudflare Images' error 5408, where direct uploads over roughly 10MB time out, the developer recommends preflight validation of size and format client-side and checking draft:true with a GET on the image ID rather than trusting a 200 response. The same pattern, they argue, should apply to agent delegation: verify scope, expiry and revocation before the call and return a refusal that names the reason.", "body_md": "United's agent ban, one more time, but from the builder's chair.\n\nSince November 11, an unauthorized AI agent cannot book, change or service a United ticket, even with the passenger supervising. United can cancel an agent-made booking without notice. The enforcement shape is the interesting part for anyone shipping agents: the check happens after the work is done. Booking made, confirmation sent, then gone.\n\nThat is the worst failure mode in any system, and you already know why from your own stack. A failure discovered after success is worse than a clean refusal up front, because everything downstream has already committed to the result.\n\nToday's corpus evidence is mundane and that is the point. Cloudflare Images direct creator uploads time out with error 5408 once a file passes roughly 10MB. The documented fix is not retry harder. It is: compress in the browser before upload, keep direct uploads under about 10MB, and validate size, format and dimensions client-side so an oversize file gets rejected with a clear message instead of a timeout nobody can act on. One more detail worth stealing: if the upload returns 200 but the image never shows in the dashboard, check for draft:true and confirm completion with a GET on the image ID. A 200 is not proof the thing landed.\n\nFull skill, with the source thread: [https://vectle.com/skills/skl_AgY6X9vSd74k-OMOKOq7dg](https://vectle.com/skills/skl_AgY6X9vSd74k-OMOKOq7dg)\n\nMap that onto delegation and the United argument mostly dissolves. The passenger side is right that consent was given: money, miles, explicit instruction. The United side is right that a borrowed password cannot express scope and cannot distinguish user, agent and fraud bot. Both of those are arguments for checking a scoped permission before the action, not for canceling the result after it. Preflight validation is a solved pattern everywhere else in the stack. Delegation is just late to it.\n\nIf you ship agents: validate the permission like you validate the payload. Scope, expiry and revocation checked before the call, a refusal that names the reason, and a human step reserved for the parts that are legally personal. Do not build the version that succeeds silently and gets unwound later.\n\nWe publish skills like the Cloudflare one, distilled from real agent debugging threads, at [https://vectle.com](https://vectle.com), and we argued the passenger versus airline sides on this week's Skill Report: [https://open.spotify.com/episode/3fYLN1Q1kcenw0EDrhWJwz](https://open.spotify.com/episode/3fYLN1Q1kcenw0EDrhWJwz)\n\nQuestion for the comments: if you told your agent to book it, with your money and your miles, should an airline be able to cancel the booking just because an agent made it, or should a ban hold until agents carry a scoped, revocable permission the airline can verify up front?", "url": "https://wpnews.pro/news/error-5408-is-a-design-review-check-the-limit-before-you-send-it", "canonical_source": "https://dev.to/vectle/error-5408-is-a-design-review-check-the-limit-before-you-send-it-3ka5", "published_at": "2026-11-22 16:06:51+00:00", "updated_at": "2026-11-22 16:12:48.809324+00:00", "lang": "en", "topics": ["ai-agents", "ai-safety", "ai-tools"], "entities": ["United", "Cloudflare", "Cloudflare Images", "Vectle"], "also_reported_by": [], "takeaway": "Validate agent permissions before the action the way you validate payloads: check scope, expiry and revocation up front, return a refusal naming the reason, and confirm completion with a follow-up GET rather than trusting a 200.", "recommendation": {"advice": "Check an agent's scoped permission, expiry and revocation before it acts, and confirm completion with a follow-up read, so failures surface as clear refusals instead of silently unwound successes.", "playbook": "agent-architecture", "playbook_url": "https://wpnews.pro/playbooks/agent-architecture"}, "alternates": {"html": "https://wpnews.pro/news/error-5408-is-a-design-review-check-the-limit-before-you-send-it", "markdown": "https://wpnews.pro/news/error-5408-is-a-design-review-check-the-limit-before-you-send-it.md", "text": "https://wpnews.pro/news/error-5408-is-a-design-review-check-the-limit-before-you-send-it.txt", "jsonld": "https://wpnews.pro/news/error-5408-is-a-design-review-check-the-limit-before-you-send-it.jsonld"}}