Release notes

A ready project has text on every page0.15.1

An import that was interrupted at the wrong moment could report ready while some of its pages had no text. Layr now finishes those pages before it calls a project ready, and the import retry repairs a project that is already in that state.

2026-09-22Patch1 change commit1 migration

Highlights

Ready means every page has its text

Before, an import could stop between saving a batch of pages and saving their text. The next attempt skipped that batch, and the project went ready with pages you could open but not search or navigate. On dev one large project lost text on 150 of 370 drawing pages and 550 of 1,009 spec pages, with no error shown. Now a batch only counts as done once its text is saved, and a project cannot reach ready until every batch is.

The import retry repairs a project that is missing text

Run the import retry on a ready project that has pages without text, and Layr redoes the text for those pages only. It does not upload the page files again. On a healthy project the retry still does nothing.

Fixes worth naming

When an import attempt loses its place in the queue to a newer attempt, it now stops instead of finishing work the newer attempt owns. That was one way a project could be finished twice.
When an import attempt fails, the reason is written to the worker log. Before, a later attempt that succeeded erased the only record of why the first one failed.
The import worker talks to the database over separate HTTP/1.1 connections, as uploads already do. One failed request can no longer break the others running beside it, including the one that keeps the attempt's place in the queue.

Upgrade notes

CI applies migration 094_import_range_text_gate.sql to production before it deploys the import worker. Dev already applied it. The migration adds document_import_ranges.text_published_at and marks every existing batch whose pages all have text as done, so healthy projects need nothing.
Batches with pages still missing text stay unmarked. Those projects still show as ready. To repair one, run the import retry for it: POST /api/project-imports/<import id>/finalize.
The import worker cap is unchanged. Production keeps IMPORT_RANGE_WORKERS=1 in the Modal layr-pipeline secret. Nothing to set.
An import that is running while production deploys may fail its last step once and retry by itself. The retry fills in the missing text.

Known limits

Layr does not find or repair affected projects on its own. The project page shows no Retry button once a project is ready, so someone with access has to run the import retry for each one.
This release fixes what an interrupted import leaves behind. It does not change why imports get interrupted. The single-worker cap from 0.15.0 is still a temporary workaround.