Release notes

Safer processing recovery0.11.0

Recover individual local processing jobs safely, control editor settings visibility, and keep first-project uploads running through list refreshes.

2026-09-10Minor9 change commits1 migration

Highlights

Diagnose and recover local processing

Local development commands now explain unfinished processing and can retry one eligible page job without resetting its project. Retried work rejects stale workers trying to publish results or change its status.

Control the editor settings wheel

The settings wheel and Settings tab are hidden by default. Administrators can restore them with the instance-wide Editor settings wheel flag. Scale calibration remains available.

Fixes worth naming

Creating your first project no longer replaces an active upload with a blank form when the project list refreshes.
Local readiness checks identify missing worker configuration, and service refresh and cleanup better respect which checkout owns the running services.

Upgrade notes

Migration 087_targeted_processing_recovery.sql adds delivery ownership, retry history, and protected job control and publication. CI applies pending migrations before deploying the app and Modal workers in each environment.
The new ui.editorSettings flag defaults to false, including for existing configurations without the field. Enable Editor settings wheel in Admin to restore the controls.
No dependency changes. The feedback-to-Slack change already on production is preserved in this release.

Known limits

The targeted retry CLI supports local page jobs only. Other processing runs require their existing recovery controls.
A queued retry is not a completed job. Jobs with a live delivery cannot be retried, and external model work may repeat after a crash.