Skip to content

Fix org-contacts UUID format and add OrgID troubleshooting guidance #5

Open
mycollablab wants to merge 4 commits into
Cloverhound:mainfrom
mycollablab:main
Open

Fix org-contacts UUID format and add OrgID troubleshooting guidance #5
mycollablab wants to merge 4 commits into
Cloverhound:mainfrom
mycollablab:main

Conversation

@mycollablab

Copy link
Copy Markdown
Contributor

Fix org-contacts UUID format and add OrgID troubleshooting guidance and add auto-wait for 429 retry with max reties and wait

mycollablab and others added 4 commits June 29, 2026 10:09
The /contacts/organizations/{orgId}/* API requires UUID format, not the
base64 format used by most other Admin endpoints. The codegen was sending
base64 because the blanket --org-id → base64 rule in root.go applied to
all non-CC commands indiscriminately.

Fix: extend the orgId normalization condition in generate_cli.py to also
apply UUID handling (--orgid flag, {orgid} path) for any endpoint whose
path contains /contacts/organizations/, matching the explicit Postman note
"orgId used in path are the org UUIDs." All 7 org-contacts commands now
use --orgid and auto-receive a decoded UUID from root.go.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Documents the CC=UUID vs admin/calling=base64 rule and tells the model
to try the other format when an API returns a 400/404 org-related error.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
On a 429 response the client now reads the Retry-After header (seconds),
sleeps that long, and retries up to 3 times. Falls back to 5 seconds if
the header is absent or unparseable. Prints a message to stderr so the
user knows why the command is pausing.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Adds two new persistent flags to control retry behavior on HTTP 429 responses:
- --max-retry (default 3): max number of retry attempts before giving up
- --max-retry-timer (default 60s): max total seconds allowed across all retries

If either limit would be exceeded before the next retry, the command exits
immediately with a clear error message stating the throttle condition and how
long to wait before retrying, rather than silently sleeping through it.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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