Release notes: 4.0.15
Changes since 4.0.14 (4 to 11 October 2026).
Highlights
Workspace snapshots show live progress and can be stopped. Processing is paused while a snapshot runs, so a snapshot never captures half-processed data. Clearer Teams and Shopping Carts pages when Public Access is on. New
Snapshot progress, stop, and failure details
The Snapshots settings page now breaks a snapshot down by stage (CAD files, bookmarks, illustrations projects, configurator projects, service parts, price lists, machines, attachment and SBOM files, parts pages, dependencies, hotspots, and settings).
Each stage shows whether it is pending, running, done, failed, or stopped, with a progress percentage and an estimated time left. You can stop a snapshot while it is still being created. A stopped snapshot shows who stopped it and when. It can’t be restored or published, so delete it and create a new one if you still need it. A failed snapshot highlights the stage that failed. Processing is paused while a snapshot runs (desktop)
Processing files and creating or restoring a snapshot both read or overwrite workspace data, so the desktop app now refuses to process files while a snapshot job is in progress. You will see a “Can’t process right now” message; try again once the snapshot finishes.
If the app can’t confirm whether a snapshot is running, it blocks processing as well and asks you to try again.
Teams and Shopping Carts explain why they are inactive
When Public Access is on, no one logs in, so Teams and Shopping Carts can’t be used.
The Teams and Shopping Carts sidebar items are always visible now. Each page shows a notice explaining that the feature is inactive because Public Access is on, and where to turn it off. The Public Access section moved to the top of the Publish page. Fixes
Parts pages: the image now stretches to the full width of its container on wide screens instead of leaving empty space. Service part pages (navigation): fixed a crash when opening the page before workspace settings finished loading. Hotspots: hotspots loaded in bulk for several items are now matched to the correct item, in the order they were requested. API changes
For anyone integrating with the Zea Core API directly.
New endpoints
Changed behavior
Snapshot job progress is now an object, not a number. This affects getWorkspaceSnapshotJobs, getWorkspaceInProgressSnapshotJobs, and the snapshot-jobs/watch stream. It was a single number; it is now { stages: [...] }, where each stage has name, title, startedAt, finishedAt, doneCount, and totalCount. Update any code that reads progress as a number. Snapshot jobs have three new fields: stoppedAt, stoppedByEmail, and errorMessage. Restoring a stopped snapshot responds 409, like one that is unfinished or failed. snapshot-jobs/watch sends at most one message per second. Rapid changes are coalesced, and the latest state is always delivered. POST /v1/hotspots/dependencies/bulk is now keyed by dependency id. The response was documented as an object keyed by dependency id, but was actually keyed by request position ("0", "1", and so on). It now matches the documentation, and a dependency without hotspots answers with []. If you worked around the old shape, switch to looking results up by dependency id.
Upgrade notes
The web app, desktop app, and API are all versioned 4.0.15 and should be updated together. The new snapshot progress shape requires the matching API version. 
