Files
twenty/packages/twenty-apps
nitin 4137a1f9fc Stop classifying Recall bot-detection timeouts as NOT_RECORDED in call-recorder (#23812)
Removes the two `timeout_exceeded_only_bots_detected_*` sub codes from
`NOT_RECORDED_RECALL_SUB_CODES`, so a bot-detection leave is handled
like any other call ending (`call_ended` -> PROCESSING -> artifact
import -> COMPLETED).

These sub codes are leave reasons, not capture verdicts. Bot detection
only fires when participants are present (otherwise `noone_joined` fires
first), and any participant starts the recording, so a bot-detection
ending virtually always has a real recording behind it. It is also the
app's own configured exit path whenever a third-party notetaker
(Fireflies, Otter) lingers after the humans leave, since a lingering bot
keeps `everyone_left_timeout` from ever firing. Classifying it as
NOT_RECORDED stamped successfully recorded calls as failures and skipped
artifact import; bots in the production Recall workspace end with this
sub code near-daily.


<!-- This is an auto-generated description by cubic. -->
<a
href="https://cubic.dev/pr/twentyhq/twenty/pull/23812?utm_source=github"
target="_blank" rel="noopener noreferrer"
data-no-image-dialog="true"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source
media="(prefers-color-scheme: light)"
srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img
alt="Review in cubic"
src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a>
<!-- End of auto-generated description by cubic. -->
2026-08-05 13:54:42 +00:00
..