Skip to content

fix: retry on queueing state without CID (Gems support)#299

Open
hiyukoim wants to merge 1 commit intoHanaokaYuzu:masterfrom
hiyukoim:fix/gem-queueing-retry
Open

fix: retry on queueing state without CID (Gems support)#299
hiyukoim wants to merge 1 commit intoHanaokaYuzu:masterfrom
hiyukoim:fix/gem-queueing-retry

Conversation

@hiyukoim
Copy link
Copy Markdown
Contributor

@hiyukoim hiyukoim commented Apr 9, 2026

Summary

When using Gems (generate_content(gem=...)), the model may enter a queueing state
where no conversation ID (CID) is available for recovery. Previously this raised
APIError immediately. Now it retries the request, giving the model time to process.

Testing

  • ✅ Predefined gems (brainstormer, coding-partner)
  • ✅ Custom user gems
  • ✅ No regression without gem parameter

When using Gems, the model may enter a queueing state where no CID is
available for recovery. Previously this raised an APIError immediately.
Now it retries the request when queueing is detected and no text has
been generated yet, giving the model time to process.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
@hiyukoim hiyukoim changed the title fix: retry on queueing state without CID instead of raising error fix: retry on queueing state without CID (Gems support) Apr 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant