Hampus_Nygren | 2022-10-05 13:10:18 UTC | #1
Hi,
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.
John_Carnell | 2022-10-05 13:30:56 UTC | #2
Hampus_Nygren, post:1, topic:16598
/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.
Hi Hampus,
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.
@Richard.Schott Any thoughts on the above problem?
@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.
Jason_Mathison | 2022-10-05 13:48:10 UTC | #3
Hi Hampus,
What topic are you triggering on?
--Jason
Hampus_Nygren | 2022-10-05 13:49:30 UTC | #4
Hi @Jason_Mathison
v2.detail.events.conversation.{id}.acw
Kind regards! //Hampus
Jason_Mathison | 2022-10-05 14:46:14 UTC | #5
I agree with John that you should open up a case with are to figure out why this API is occasionally failing.
In the data action error path in your flow you could try adding a wait and then retry the data action.
--Jason
Hampus_Nygren | 2022-10-06 06:35:09 UTC | #6
Thank for the answers, I will do as you suggest.
I wish you a great day!
Hampus_Nygren | 2022-10-06 07:16:04 UTC | #7
Hi,
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.
John_Carnell | 2022-10-06 14:49:12 UTC | #8
This post was migrated from the old Developer Forum.
ref: 16598