Resolved Issues

Incident

Resolved Issue

STNG-8251

In rare cases where a node was deactivated or upgraded, recorded calls could remain stuck in “Recording” until a nightly sweep.

STNG-8275

Some interactions were marked as Failed in the Interaction Recordings portal when the recording bot restarted during post‑processing.

STNG-8301

When the profile cache was unreachable, the bot treated it as if users had no recording profile, stayed in the call, and did not record; the cache could remain wedged for days without alerting or self-healing.

STNG-8343

The Interactions page displayed only primary recordings; if the primary leg was missing, a call could take up to 20 minutes to appear after automatic promotion of the secondary leg.

STNG-8468

Selecting a saved search that included multiple Statuses or Tags showed an empty results list (“No rows”) even when matching recordings existed; refreshing the page or opening a shared link with those filters also returned no results. Clearing the saved search could leave stray text in the address, causing “Reset Search” to appear when nothing was filtered.