MIR-956

`miren app list` crash count doesn't clear after successful deploy

Done public

phinze Opened Apr 2, 2026 Updated Apr 2, 2026

Preserve LastCrashTime when resetting crash state on pool

Summary

After an app recovers from a crash loop (new version deployed successfully, sandbox running, serving traffic), miren app list continues to show crashed (Nx, retry Xs) status. The crash count from previous failed sandboxes persists.

Example

uptime-kuma was crash-looping due to MIR-950 (disk mount bug). After the fix was deployed and the app came up healthy (SQLite connected, listening on port 3000, sandbox status running), miren app list still showed:

uptime-kuma  uptime-kuma-vCZfFygWRPditniT2DE55T  crashed (3x, retry 20s)

Meanwhile miren sandbox list --all showed the new sandbox as running.

Expected behavior

Once a new sandbox is running and healthy for a version, the crash status should clear and show the normal running state (e.g., 1 (fixed)).