Skip to content

fix: rollback failed notification interaction with visual warning - #3145

Open
setchy wants to merge 1 commit into
mainfrom
fix/state-rollback-forbidden-actions
Open

fix: rollback failed notification interaction with visual warning#3145
setchy wants to merge 1 commit into
mainfrom
fix/state-rollback-forbidden-actions

Conversation

@setchy

@setchy setchy commented Aug 4, 2026

Copy link
Copy Markdown
Member

Issue
Fix a bug whereby a notification interaction can fail [rate limit, forbidden] leaving gitify in a broken state. manual or timer notification refreshes would not recover state, only a force reload of the app.

Example
Using a GitHub Enterprise Managed User (EMU) account, that has subscribed to a GitHub Cloud (OSS) issue or pull request.
The GitHub EMU security policies prevent API interactions via PAT with GitHub Cloud content.
This throws a HTTP 403 Forbidden when performing mark as read, mark as done or unsubscribe interactions.

Before

before.mov

After
Notification state restored on failure [tanstack query]
Visual indicator on notification interaction buttons about reason for failure

Screen.Recording.2026-08-04.at.8.08.04.AM.mov

Signed-off-by: Adam Setch <adam.setch@outlook.com>
@setchy
setchy requested a review from afonsojramos as a code owner August 4, 2026 12:59
@github-actions github-actions Bot added the bug Something isn't working label Aug 4, 2026
@sonarqubecloud

sonarqubecloud Bot commented Aug 4, 2026

Copy link
Copy Markdown

Quality Gate Failed Quality Gate failed

Failed conditions
3.4% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Development

Successfully merging this pull request may close these issues.

1 participant