Investigate publish recovery after an interrupted index sync #102

Closed
opened 2026-10-05 12:50:13 +00:00 by eleith · 0 comments
Owner

Goal

Investigate how an interrupted publish recovers before choosing any implementation change.

Potential failure window: core index/cache updates succeed inside luzzle.sync, but execution stops before the durable step result is recorded. A retry may then see an empty diff despite unfinished downstream publication.

Investigation

  • Reproduce the suspected interruption with isolated fixtures and controlled failure injection.
  • Distinguish replay after a completed checkpoint from retry before that checkpoint, and from a fresh publish after failure.
  • Observe which pieces still reach web sync and asset generation, including relevant pruning behavior.
  • Report what existing OpenWorkflow recovery already handles and any demonstrated gap.
  • Review findings and options with the owner before changing behavior.

No work manifest, new persistent state, retry policy, or automatic full rebuild is preselected. Individual transform failures remain best-effort publication with a warning summary, not a reason to abort the publish.

## Goal Investigate how an interrupted publish recovers before choosing any implementation change. Potential failure window: core index/cache updates succeed inside `luzzle.sync`, but execution stops before the durable step result is recorded. A retry may then see an empty diff despite unfinished downstream publication. ## Investigation - Reproduce the suspected interruption with isolated fixtures and controlled failure injection. - Distinguish replay after a completed checkpoint from retry before that checkpoint, and from a fresh publish after failure. - Observe which pieces still reach web sync and asset generation, including relevant pruning behavior. - Report what existing OpenWorkflow recovery already handles and any demonstrated gap. - Review findings and options with the owner before changing behavior. No work manifest, new persistent state, retry policy, or automatic full rebuild is preselected. Individual transform failures remain best-effort publication with a warning summary, not a reason to abort the publish.
eleith added the bug label 2026-10-05 12:50:13 +00:00
eleith changed title from Retain publish work across an interrupted index-sync checkpoint to Investigate publish recovery after an interrupted index sync 2026-10-05 23:14:51 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: eleith/luzzle#102