Reliability, performance and offline
Reliability
Failure and recovery.
Status labels: Live (checked directly, dated) Built in code; not independently verified In progress Planned, not shipped Open decision or unverified Not offered / no claim made
C0568 What happens if ET crashes?
We have not documented crash recovery. Project locks let you restore a desk, so save often, but autosave is not claimed.
C0569 Does ET autosave my desk?
Not documented. A project lock is an explicit named save, so treat it as a manual action.
C0570 Has ET been load tested?
Not applicable in the usual sense, because it is a local desktop app with no ET server, and no stress tests are published.
C0571 Does ET have a single point of failure?
The sign-in depends on the account host, and pictures' fallback depends on the media host. The rest is local, so failure there does not stop local exploration.
C0572 Are there known bugs?
A polish list exists: stale version and count labels, map load for large boundary files and extraction behaviour. We have not published a complete bug list.
C0573 How are problems found?
By local testing. There was no automated build pipeline as of late August 2026, and tests run on a developer's machine.
C0574 How many tests pass?
Build notes report passing tests for specific changes, for example a login change with 119 desk tests. We do not quote an overall pass rate.
C0575 Can you show me test results?
Not publicly. We do not publish test logs, and the site only repeats statements from project notes, with dates.
C0576 What if the account host is down?
You cannot sign in until it returns. ET cannot work around that, since it does not hold accounts.