Thanks — I see you're reporting an egress that's showing as ACTIVE in the dashboard (EG_CAcnaRCkdTKx, duration ~149 min) while the recording is already available, and

lk egress stop

returned: "failed_precondition: egress with status EGRESS_COMPLETE cannot be stopped." I'll help you troubleshoot. Short answer • The error means the egress is already recorded/completed on the backend (status EGRESS_COMPLETE) and cannot be stopped because stopping applies only to active egresses. The UI still showing "ACTIVE" and the increasing duration is likely a stale or mismatched UI state rather than an actually running egress. What you can check next 1. Confirm backend state via webhook/API ◦ Check whether you received an

egress_ended

webhook for this ID (it includes final status and any backup manifest info). ◦ Or call the egress status endpoint (or list egresses) to see the server-side status for EG_CAcnaRCkdTKx. 1. Verify recordings/destinations ◦ If the recording file(s) are present or a backup manifest was provided, the egress has completed successfully even if the dashboard still shows active. ◦ If uploads failed, look for

backupStorageUsed: true

and a manifest location in the

egress_ended

payload. 1. UI troubleshooting ◦ Try refreshing the dashboard (or disable any cached UI state / turn auto-refresh on) — the UI can lag behind the backend. ◦ If you have multiple LiveKit deployments or environments, confirm you're viewing the same environment that created the egress (screenshot shows leigo_prod). If you'd like, tell me: • Whether you received an

egress_ended

webhook for this ID (yes/no) and any fields from it (status, backup manifest). • Whether the destination shows files or a backup manifest URL. With that info I can help interpret the webhook/manifest or suggest next steps to clear the UI state and confirm there's no active process incurring cost. Sources: Backup Egress Recordings | Universal Egress | LiveKit, with interactive elements

I menat livekit lk command like "lk egress status --id `EG_CAcnaRCkdTKx`" something like this