---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/13621#article
headline: "13621: Invalid 'recordingStatusCallbackEvent'"
url: https://www.twilio.com/docs/api/errors/13621
inLanguage: en
dateModified: 2026-03-20T20:33:25.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 13621: Invalid 'recordingStatusCallbackEvent'

Log Level: ERROR

## Description

Twilio returns this error when one or more values in `recordingStatusCallbackEvent` are invalid. Valid values are `in-progress`, `completed`, and `absent`. If you set `recordingStatusCallback` without `recordingStatusCallbackEvent`, Twilio sends `completed` by default.

### Possible causes

* `recordingStatusCallbackEvent` includes a value other than `in-progress`, `completed`, or `absent`.
* Multiple callback events are separated with commas or another delimiter instead of spaces.

### Possible solutions

* Update `recordingStatusCallbackEvent` to use only supported values, separated by spaces, such as `in-progress completed`.
* Remove `recordingStatusCallbackEvent` if you only need the default `completed` callback.

#### Additional resources

* [TwiML Voice: `<Recording>`](/docs/voice/twiml/recording)
* [TwiML Voice: `<Record>`](/docs/voice/twiml/record)
