Additional validation for in-queue and Customer First Callback related flows submitted in the queue object

Description

Additional validation will be enforced on the flows submitted during creation or update of queues.

Related Public API endpoints:

  • POST /api/v2/routing/queues

  • PUT /api/v2/routing/queues/{queueId}

Related fields:

  • queueFlow

  • emailInQueueFlow

  • messageInQueueFlow

  • mediaSettings.callback.liveVoiceFlow

  • mediaSettings.callback.answeringMachineFlow

When submitted, the flows will be checked for being present (created), being published and having a matching type.

Change Category

API

Change Context

This update is long overdue, without the change the flows are unchecked when submitted using Public API and customers may face unexpected results due to misconfiguration.
The same validation criteria are already enforced in the UI.

Change Impact

Submitting an invalid flow during an update or creation will result in a failure.
If the queue is already configured with the flow that is invalid and the same value is submitted, the update will also fail.

Date of Change

30 Jun 2025

Impacted APIs

POST /api/v2/routing/queues
PUT /api/v2/routing/queues/{queueId}

References

[AS-1909]