I have implemented a process automation trigger which executes a workflow.
Within this workflow I use a data action to fetch conversationEnd from /api/v2/analytics/conversations/${input.conversationId}/details
It seems to work most of the time, but sometimes it fails with "The requested resource was not found.". The conversationId provided is correct and if I execute the data action manually with the conversationId everything is ok.
I would open a ticket with our customer Care team. This sounds suspiciously like a data race or eventual consistency problem in the conversation service, but I would need the engineering team responsible for the service to do a deeper investigation.
@Jason_Mathison Are there any retry patterns we could do with a flow and a data action to wait X seconds on the event of a 404 and then retry the call X times? It is not a solution, but it might be something that could help until the engineering team could investigate further.
When I requested our partner to submit a case, they asked why I was using the analytics endpoint. They said that there could be a delay before interactions show up there.
I have no reason to use the analytics, so I switched to /api/v2/conversations/{conversationId} instead.
I keep my fingers crossed that that this will solve the issue.