Queue behavior
Drafts process sequentially. If one is running, the next will queue.
Large repos may take longer to index the first time.
Queued drafts will start automatically once the current job finishes.
What to try before refreshing
Confirm the tag exists and points to the correct commit.
Check GitHub status if you see repeated delays.
Wait a few minutes for large repos before clicking Refresh.
Refresh safely
If a draft is stuck, wait a few minutes and then click Refresh.
Avoid repeatedly clicking Generate while a draft is active.
When to contact support
If the queue is stalled for more than 30 minutes, contact support with the repo name and tag.
We can inspect job logs and unlock the queue if needed.
Review and introspect
Queues are calm when release inputs are stable.
- Do you know which repo caused the queue to stall?
- Are you timing refreshes to avoid duplicating work?
- Would a documented release window reduce queue contention?