This repository was archived by the owner on Mar 26, 2026. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 77
Paged requests do not use routing header metadata #469
Copy link
Copy link
Labels
🚨This issue needs some love.This issue needs some love.conversion blockingA surface delta, bug, missing feature, or other issue that prevents API conversionA surface delta, bug, missing feature, or other issue that prevents API conversionpriority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.Important issue which blocks shipping the next release. Will be fixed prior to next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Metadata
Metadata
Assignees
Labels
🚨This issue needs some love.This issue needs some love.conversion blockingA surface delta, bug, missing feature, or other issue that prevents API conversionA surface delta, bug, missing feature, or other issue that prevents API conversionpriority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.Important issue which blocks shipping the next release. Will be fixed prior to next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Currently blocking the KMS conversion.
For paged requests, the initial request includes the routing header but subsequent requests do not. Some APIs (KMS) appear to require the routing metadata on every request.