Story: Feeds start and restart the same way every time
Table of Contents
This page documents a story in Sprint 28. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
1. Goal
Close the faults that the stop and start test of every feed group found, so that each group shows the documented behaviour.
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 28 |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-10-19 |
3. Acceptance
- A restart with marketdata not yet running starts every auto-start feed once marketdata answers.
- A provision starts the system feeds without a restart.
- A person's Start of a feed creates the binding of the person's party.
- Reporting creates its run grant through the shared client call.
- Every feed group shows the documented behaviour across a stop and a start of the services.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Scaffold story: Feeds start and restart the same way every time | DONE | 2026-10-19 | 2026-10-20 | Story scaffolding rides this task: documents, sprint wiring, and the scaffold PR. Close it before merging that PR. |
| Implement feeds that start and restart the same way | DONE | 2026-10-20 | Initial task for: Feeds start and restart the same way every time |
5. Decisions
- The
enabledandauto_startflags stay the only stored form of the running set. A Start or a Stop by a person does not survive a restart. - A restore tries again for every feed that fails, except a feed whose series another feed holds.
- A provision calls the restore as an operation, once, and never fails because of it.
6. Out of scope
- Revoking a run grant when its collection is deleted. The delete is generated code that has no IAM call. Capture: revoke_a_collections_run_grant_on_delete.
- A check that the consenting person's party matches the collection's party.