Queue basics
The build queue tracks construction intents in order. Submitting a build request does not always mean instant completion; queued work resolves according to tick processing and queue rules. This creates predictable sequencing and prevents conflicting build mutations from applying simultaneously.
When multiple items exist, read the queue top-down. Earlier entries usually gate later completion.
Ticks remaining
Each queued item should show progress in ticks remaining or an equivalent status indicator. Ticks remaining is the most reliable timing signal because it reflects server-side cadence, not browser timers.
If you need a change by a specific point, count ticks backward and queue early. Waiting until the last moment often causes avoidable timing misses.
Cancel + refunds
Cancellation is usually allowed only while an item is still cancelable by queue state. Refund behavior depends on policy: some states return full cost, some partial, and completed items are normally not refundable.
Always verify cancel result in Outcomes. Do not assume a click means successful rollback; you need the processed event confirming cancel and refund amount.
Troubleshooting
If cancel fails or progress looks wrong:
- Confirm you targeted the correct queue item.
- Check whether the item already completed on a recent tick.
- Review error/reason message for non-cancelable states.
- Refresh queue view after tick rollover.
- Use Outcomes to validate whether a refund was actually applied.