Publishing re-processed datasets no longer holds the database
OrionAI 2.44.1Released 7 November 2026
When a re-processed dataset is put live, Orion Core no longer keeps a database transaction open while the web app draws or moves its pictures.
Changes since 2.44.0.
#Fixed
- Putting a re-processed version live no longer holds the database while pictures are drawn.
Before, the publish job kept a transaction open on the dataset record while the web app drew the
new version's pictures and moved them into place. If the web app restarted at that moment, its
start-up check of the dataset table waited behind that transaction, and so did every page that
reads datasets. On 2026-11-07 this made the site unavailable until the stuck session was ended.
Now the job:
- checks the new version and commits before it calls the web app;
- locks the record again only to write the new version; and
- writes it only if the version is still the one it checked. A version changed in the meantime is held and checked again on the next run.
- As a safeguard, the database ends the publish job's session if it ever sits idle inside a transaction for more than 60 seconds.