Extend App Version Stays In-Flight and Waiting To Be Scheduled
The error Version: In-flight
Status: Waiting to be scheduled
What does "Extend App Version Stays In-Flight and Waiting To Be Scheduled" mean in Workday Extend?
You released a new version of an Extend app, but instead of deploying, App Manager shows the version as In-flight with a status of Waiting to be scheduled. Nothing has failed; the install is queued.
Quick fix
Confirm the app carries a Model component, then wait for the next weekend maintenance window. Release model-bearing versions as soon as they are ready so they sit in the queue rather than missing the window.
Permanent fix
Plan Extend releases around the maintenance window whenever the app contains Model components. Ship model-bearing versions early in the week, and split pure presentation changes into their own versions so those can deploy without waiting on the window.
Troubleshooting
- Check whether the app contains a Model component such as a custom business object, business process, model task or model report. Only apps carrying Model components queue this way.
- Look at which tenant you are deploying into. The queue applies to implementation tenants and above, so the same app can install straight away in one tenant and wait in another.
- Confirm the version was actually released rather than only saved. A version that was never released shows no deploy state at all, which is a different problem.
- Compare the release date against the tenant's weekend maintenance window. If that window has not passed since you released, waiting is the expected outcome and there is nothing to fix.
- If the window has passed and the state has not moved, re-read the status from the App Manager task rather than the developer view, because the two can lag each other.
- Treat it as a defect worth raising only after a full maintenance window has passed with no change in state.
Was this helpful?