Surface a stale connector without logging vendor payloads
A connector has not completed a refresh for six hours, yet its status is green because the last HTTP request succeeded. Define freshness from completed ingestion checkpoints.
- Focused work estimate
- 1h 45m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Observability · Freshness semantics · Secret handling
Estimated field mix
- Site reliability50%
- Integrations50%
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 retailer receives stock from two vendor warehouses. The vendor API paginates snapshots and emits change events, but retries and deleted products have caused unexplained stock drift. Work against a local vendor simulator.
Setup prerequisites
- Create a local vendor API simulator with cursor pages and stock events.
- Use synthetic tenants, SKUs, and warehouse records; no vendor account is required.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Status exposes last complete snapshot, latest accepted event, current attempt, and safe failure category separately.
- A configured freshness threshold marks stale data without claiming the connector is healthy from HTTP success alone.
- Metrics and logs exclude tokens, raw payloads, and customer-specific product descriptions.
Implementation constraints
- Use UTC and an injected clock for freshness.
- Keep metrics cardinality bounded; item IDs belong in scoped diagnostics.
Verification to include
- Advance the clock past the threshold after a partial refresh and verify stale status.
- Cause a vendor error containing a token marker and confirm it is absent from all normal diagnostics.
Deliverables
- Connector health projection and safe diagnostic tests
Rollout and recovery
Publish status before enabling notifications; reset health only after a complete qualifying ingestion checkpoint.
Value of the work
For the engineer: Practice external contracts, cursor recovery, mapping conflicts, and reconciliation under partial failure.
For the team: Inspect whether integration changes protect inventory correctness and give operators a clear recovery path.
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.