Workspace keeps running after archive action on long-lived workspaces

Description:
When a workspace has been running for a long time, usually 1 day or more, clicking Archive does not stop the container. The workspace keeps running even though the Codex mux setting in Coder is configured correctly.

This does not seem to happen with recently created workspaces. For new workspaces, creation and deletion work as expected. The issue appears only on older, long-running workspaces.

Expected behavior:
Archiving the workspace should stop the container and start the deletion flow.

Actual behavior:
The workspace continues running after archive is triggered.

Additional context:

The issue seems to affect long-lived workspaces only.

I suspect this may be a Codex mux issue, because the archive action does not affect the running container.

I’m using Bazel, so the workspace cache and volume can grow very large over time, sometimes up to 300 GB.