Hello,
I have an integration that adds an attribute to the current call of the agent and then conferences a flow using POST /api/v2/conversations/{conversationId} participants, with a body like:
{
"participants": [
{
"address": "flowname@localhost"
}
]
}
When done with my development environment in the us-east-1 region this works like a dream. However, when deployed in ca-central-1 the API calls work fine, attributes are added and the conference is initiated but, the flow does not work.
In the ca-central-1 region the flow cannot read or write participant data and it cannot find a user prompt. This was confirmed with a flow that has hard coded values for the participant data to write and the user prompt to find.
If the agent performs a blind transfer to the same flow in ca-central-1 the flow can perform these operations.
The application uses an authorization code grant with the users-basic-info and conversations scopes. The user in both environments were given all permissions as part of this test.
What could be causing the difference between the regions?