Skip to content
KiweelyKiweelyKiweely

Codex for Orchestration JSON: Catching the 25-Second Sync Trap Before Deploy

Before deploying orchestration JSON, check for synchronous page calls that will hit Workday’s 25-second limit on long external AI calls.

  • By Kiweely
  • Updated
  • 1 min read
On this page

kiweely.com and Workday community debugging already document the 25-second synchronous orchestration limit when Extend pages call long external work. Any coding agent editing orchestration JSON should grep for sync patterns that call OCR/LLM APIs and insist on async design before deploy.

Agent checklist

  • Is this orchestration launched sync from a PMD?
  • Does any step call an external model or heavy HTTP that can exceed 25 seconds?
  • If yes, redesign to async before Save and Deploy.

Shipping sync LLM calls is a production incident scheduled for the first slow response.

Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.

We’ll email you once to confirm. Unsubscribe in one click from any issue.