Skip to content

fix: send required scope for batch schedule archive - #16

Merged
moonyue-w merged 1 commit into
mainfrom
codex/contract-bug-fixes-20261120
Nov 21, 2026
Merged

moonyue-w merged 1 commit into
mainfrom
codex/contract-bug-fixes-20261120

Conversation

@moonyue-w

Copy link
Copy Markdown
Contributor

Change

schedules().archiveMany(...) now always sends "scope": "by_schedule_ids" together with schedule_ids, matching the official contract. This scope is required and has no server default; previously the SDK sent only schedule_ids, resulting in HTTP 400 invalid_request. Existing callers need no code changes.

Correct the Javadoc, Schedule/Batch guide and CONTRIBUTING guidance that incorrectly stated the service rejects scope. The request contract tests cover both synchronous and asynchronous methods, retaining the existing ID bounds, deduplication and idempotency header.

This is Java-specific: Go exposes the scope and Python/TypeScript inject it. No incompatible API or version change is included.

Validation

  • SDK build, tests and Javadoc pass.
  • Independent examples consume the installed JAR and pass.
  • Java 8 package check passes; changed behavior checked on Java 8 and 17.
  • Documentation and changelog reflect the behavior change.
  • make quality passes on JDK 17.
  • Version updates: not applicable; no version change.
JDK 17.0.17: make quality  # passed
JDK 17.0.17: make test     # SDK tests, examples and package check passed
JDK 8u452:   make test     # 1257 SDK tests, 76 example tests, package check passed

No live scenarios were run; these are offline wire-contract and packaged-consumer checks, not production acceptance.

The Forward service rejects batch archive requests without
scope=by_schedule_ids, so archiveMany failed with HTTP 400 on every call.
Always send the fixed scope and correct the docs that claimed the server
rejects it.
@moonyue-w
moonyue-w merged commit 156cf5b into main Nov 21, 2026
17 of 18 checks passed
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