Change feeds and replay
What the upstream source has changed since this deployment last read it, and replaying a window of it.
Note: This screen has no data behind it in this build
The address is specified and the console is ready for it. What is missing is the server side: the reads below are declared by the contract and are not registered in this deployment, so they answer “not implemented” rather than returning anything. Nothing on this page is a placeholder for data — there is no data to place.
What this screen is for
The change feed each connection exposes — what changed upstream, when, and whether this deployment has consumed it — with a previewed replay of a window when something was missed or processed wrongly.
What has to exist first
- Reads
- staffChangeFeedGet
- Actions
- staffChangeReplayPreview
- staffChangeReplayCommit
Each of those is an operation id in the frozen contract. Registering one is a server change, not a permission you can be granted — no group and no scope makes this screen return data today.