Flush the gateway's cached decisions
What It Does
Flushing accelerates eventual consistency but does not establish immediate revocation. The workflow records submission, configured-stage iteration and the gateway reset result separately.
The Flow
The diagram separates the relevant success, alternative and failure paths. The numbered hop rows retain the detailed authority checks, delegated work and retry limits.
When Something Fails
Acceptance proof must include traffic after the reset; a successful provider response alone is insufficient. Previously issued signed contexts retain their own validity bound.
Each new change receives a new submission identity; retrying that submission returns its job. Repeating the gateway reset is intended to converge, but reported success alone does not prove eviction.
Flush jobs may overlap and do not share an open-job exclusion. The task attempts every configured API stage and aggregates failures before returning.
Open Design Questions
The recorded findings retain any stronger planning expectation, missing writer or unproved recovery path. Observed behavior does not approve those outstanding product choices.