Varun_Ghaswala | 2023-08-29 03:02:29 UTC | #1
Hey,
We are currently integrating OpenMessaging in Genesys with our internal systems and seeing some strange behaviour on the .NET SDK. (v184.2.0)
When we attempt to fetch message details using GetConversationsMessageDetailsAsync for a message that was just created using PostConversationsMessagesInboundOpenAsync we are often seeing a 404 Not Found.
We have had to add delays to the second call which then seems to return responses correctly.
The code for this sequence looks something like this:
public async Task<string> CreateConversation(OpenNormalizedMessage openNormalizedMessage){
// POST /api/v2/conversations/messages/inbound/open
OpenNormalizedMessage result = await ConversationsApi.PostConversationsMessagesInboundOpenAsync(openNormalizedMessage);
// The following call often returns a 404.
// We have had to add a delay before fetching
// await Task.Delay(1000);
// GET /api/v2/conversations/messages/{messageId}/details
MessageData messageData = await ConversationsApi.GetConversationsMessageDetailsAsync(result.Id);
return messageData.ConversationId;
}
Can you please help us understand why the API would return a 404 for something that was just generated.
Thank you
tim.smith | 2023-08-29 13:49:30 UTC | #2
This sounds like eventual consistency, but will require an investigation by Care to be sure. We don't have access to your data via the forum to look into the timing of your requests and the data, but Care does. Care will need to know the correlation IDs from the 404 responses and the conversation ID you're using in the request.
Varun_Ghaswala | 2023-08-29 21:57:31 UTC | #3
Thanks for that @tim.smith
We will get in touch with the Care team.
Cheers
system | 2023-09-29 21:57:55 UTC | #4
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 21738