stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Resume queued delivery after operator sign-in #266

New Issue
Closed
opened 2026-08-08 05:28:47 +00:00 by timmy · 0 comments
timmy commented 2026-08-08 05:28:47 +00:00
Owner
Copy Link

Problem

Background delivery authenticates, then performs a separate mutation. If the eight-hour operator session expires between those requests, the mutation returns 401 and the current worker incorrectly marks valid queued work as permanent Attention. This loses automatic delivery and requires a manual retry. Existing #250/#252 background sync and #258 operator sessions do not cover this race.

User flow

  • Treat mutation-time 401 as recoverable session expiry.
  • Release the in-flight claim, abort the drain, and keep the original idempotency key.
  • Generate no Attention receipt for authentication expiry.
  • After a successful sign-in, request background delivery again so pending work resumes automatically.
  • Preserve permanent handling for 422 and retry handling for 5xx.

Acceptance tests

  • A mutation 401 releases the claim, rejects the flush, and does not fail the item or emit Attention.
  • No later queued mutation is attempted in that drain.
  • A later authenticated flush delivers the same operation once with its original idempotency key.
  • Successful sign-in asks the service worker to resume pending delivery.
  • Existing 422, 5xx, cross-account, and race behavior remains green.
## Problem Background delivery authenticates, then performs a separate mutation. If the eight-hour operator session expires between those requests, the mutation returns 401 and the current worker incorrectly marks valid queued work as permanent Attention. This loses automatic delivery and requires a manual retry. Existing #250/#252 background sync and #258 operator sessions do not cover this race. ## User flow - Treat mutation-time 401 as recoverable session expiry. - Release the in-flight claim, abort the drain, and keep the original idempotency key. - Generate no Attention receipt for authentication expiry. - After a successful sign-in, request background delivery again so pending work resumes automatically. - Preserve permanent handling for 422 and retry handling for 5xx. ## Acceptance tests - A mutation 401 releases the claim, rejects the flush, and does not fail the item or emit Attention. - No later queued mutation is attempted in that drain. - A later authenticated flush delivers the same operation once with its original idempotency key. - Successful sign-in asks the service worker to resume pending delivery. - Existing 422, 5xx, cross-account, and race behavior remains green.
timmy self-assigned this 2026-08-08 05:32:29 +00:00
timmy closed this issue 2026-08-08 05:34:03 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#266
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?