What it means
The API answers with HTTP 400 Bad Request and the application/problem+json document below when the condition is Notification destination is not valid for its channel. The document's type member is https://screenrig.ai/problems/notification-destination-rejected, the address of this page, and its code member is notification_destination_rejected.
What to do
Give the credential the service itself issues: a Slack incoming webhook URL, a Teams Workflows webhook URL, a PagerDuty Events API v2 routing key or a Telegram bot token. The detail names the shape the channel takes.
Player action
This problem defines no Player action class. It belongs to a project, pairing or account flow that an agent or the dashboard drives.
Reference
| Code | notification_destination_rejected |
|---|---|
| HTTP status | 400 Bad Request |
| Type | https://screenrig.ai/problems/notification-destination-rejected |
| Player action | none |