Repository navigation
feat(cli): send idempotency keys on message and campaign writes - #11
Conversation
|
Warning Review limit reached
Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing. Next included review available in 59 minutes. View limit detailsLimit details: You’ve used the included review currently available. Your 75 included PR review attempts over the past 7 days set your current allowance at 1 review per hour. Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (22)
Comment |
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. Keep them coming! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
bdada86 to
4a264f4
Compare
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4a264f4b93
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex review |
|
Codex Review: Didn't find any major issues. Already looking forward to the next diff. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Summary
Message sends, reactions, edits, deletions, and campaign create/launch requests send an
Idempotency-Keyby default. Each new invocation receives a fresh key; SDK retries within that invocation reuse it. For a retry from another process, callers choose an explicit key before the first attempt and preserve the request, credential, and API version.The command help and README now describe the API's recorded-outcome behavior accurately: completed messaging writes return
409 idempotency_completedwithout the original response body. In-progress and uncertain outcomes remain fenced; a new key is not a recovery shortcut. Mark-seen, typing, star, and campaign pause/resume/stop/requeue do not gain server deduplication from this header.All eleven message-send variants generate a key. The installed npm dependency is
@polymorfa/sdk@0.1.0-dev.20260922102711, pinned in both manifests; edit/delete obtain their default key from this SDK.Six-part assessment
360afa8239140b2857f0622120dfccf2cf5de025, unchanged at63111fec728ac3ebc9a825ea57ebc4c592abdafc. No route, scope, or response shape changes.Verification
idempotency_completederror without resending or returning the original message ID.No live WhatsApp send, campaign, deployed API, or retention-expiry boundary was exercised. Exact-head hosted CI must pass before merge; publishing the CLI remains separate.