Reject invalid timeout combinations as one configuration unit
A retry timeout exceeds the entire request deadline, causing requests to continue working after callers have disconnected.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Validation · Deadline budgets
Estimated field mix
- Platform engineering80%
- Backend20%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional internal reporting platform changes feature and timeout settings through environment edits. Partial rollouts leave API and worker processes interpreting different values.
Setup prerequisites
- Create local API and worker configuration consumers.
- Use fabricated settings without secrets.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Validate relationships between attempt, retry and total deadlines.
- Reject the complete candidate snapshot on any invalid relation.
- Return field paths with safe values only.
Implementation constraints
- Use explicit duration units; reject implicit unit conversion.
Verification to include
- Accept a documented valid retry budget.
- Reject a larger attempt timeout than total deadline without changing active settings.
Deliverables
- Snapshot validator and deadline fixtures
Rollout and recovery
Add validation to drafts; preserve the active snapshot on any rejection.
Value of the work
For the engineer: Practice configuration contracts, compatibility and failure recovery.
For the team: Review controlled configuration delivery with inspectable blast radius.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.