notifications: add read.backfill.error event type - #405
Open
jlimatampersand wants to merge 2 commits into
Open
jlimatampersand wants to merge 2 commits into
jlimatampersand wants to merge 2 commits into
Conversation
Backfill read failures previously had no builder-facing event — the server published read.triggered.error for every read failure. The server now emits read.backfill.error when a backfill read fails (amp-labs/server#7312); this adds the event type to the NotificationEventType enum and defines its payload schema. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
![graphite-app[bot]](https://avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
laurenzlong
approved these changes
Sep 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the
read.backfill.errornotification event type.Context
Backfill read failures previously had no builder-facing event: the server published
read.triggered.error(documented as an on-demand triggered read failure) for every read failure, so builders subscribed to backfill lifecycle events (read.backfill.done) never learned a backfill failed. The server now emitsread.backfill.errorwhen a backfill read fails — see amp-labs/server#7312.Changes
api/api.yaml: addread.backfill.errorto theNotificationEventTypeenum.notifications/notifications.yaml: addReadBackfillErrorDataandReadBackfillErrorNotificationPayloadschemas (installation fields +objectName+error), mirroring the read.triggered.error shape minus the trigger window timestamps.pnpm run gen:json.Related
🤖 Generated with Claude Code