Preventing ECONNRESET Errors in Automated API Calls to DustAPI

Nicolas Boussenina · 2025-03-24 15:25:32.583444+00

Hello I have an automation that launches multiple api calls to Dust with an agent, and on one of the responses, I had: ERROR: Error running multi-actions agent action: [unexpected_network_error] Unexpected network error from DustAPI: Error: read ECONNRESET (code: multi_actions_error) My agent uses claude 3.5 and when I clicked on "retry" it worked. How to prevent this? Thanks!

Preventing ECONNRESET Errors in Automated API Calls to DustAPI | Dust Community

14 comments

· Sorted by Oldest

Nicolas Boussenina
·
·
Loading attachments
Nicolas Boussenina
·
·
for another api call, I had ^^'
Loading attachments
Alban
·
·
Hi, this seems to have been a transient network error. Anthropic can be a bit unstable unfortunately as they are growing a lot
Nicolas Boussenina
·
·
Thank you Alban! How can we implement a retry mechanism?
Nicolas Boussenina
·
·
in terms of the route to be used in the API what should I be doing to retry a failed response? Indeed, I need to automate certain tasks and I can't afford to have a failure
Alban
·
·
You'd need to catch the error and retry on your side
Nicolas Boussenina
·
·
I just send a message to a convo id for the moment I don't have any errors from the API as my message is well sent, but the answer never comes
Nicolas Boussenina
·
·
https://docs.dust.tt/reference/post_api-v1-w-wid-assistant-conversations-cid-messages Im using this and my message goes to the conversation (so, no error), but I'm missing the answer from the mentioned agent
Nicolas Boussenina
·
·
From my side, I’m sending the message via the Dust API, and it works as expected. Since it’s working on your end as well, Dust should be responsible for forwarding the request to the LLM and handling retries if the forwarded request fails
Alban
·
·
Hi, do you use the 'blocking=true' parameter?
Alban
·
·
If you don't, then the answer will be streamed and you'll have to catch the streaming events
Alban
·
·
https://docs.dust.tt/reference/get_api-v1-w-wid-assistant-conversations-cid-events
Nicolas Boussenina
·
·
For creating the convo yes 😄 But then I'm sending messages with https://docs.dust.tt/reference/post_api-v1-w-wid-assistant-conversations-cid-messages and there is no such 'blocking' parameter for this endpoint
Alban
·
·
Ha yes, if you are inside a conversation you have to go through the streaming events

Nicolas Boussenina
·
·
Loading attachments
Nicolas Boussenina
·
·
for another api call, I had ^^'
Loading attachments
Alban
·
·
Hi, this seems to have been a transient network error. Anthropic can be a bit unstable unfortunately as they are growing a lot
Nicolas Boussenina
·
·
Thank you Alban! How can we implement a retry mechanism?
Nicolas Boussenina
·
·
in terms of the route to be used in the API what should I be doing to retry a failed response? Indeed, I need to automate certain tasks and I can't afford to have a failure
Alban
·
·
You'd need to catch the error and retry on your side
Nicolas Boussenina
·
·
I just send a message to a convo id for the moment I don't have any errors from the API as my message is well sent, but the answer never comes
Nicolas Boussenina
·
·
https://docs.dust.tt/reference/post_api-v1-w-wid-assistant-conversations-cid-messages Im using this and my message goes to the conversation (so, no error), but I'm missing the answer from the mentioned agent
Nicolas Boussenina
·
·
From my side, I’m sending the message via the Dust API, and it works as expected. Since it’s working on your end as well, Dust should be responsible for forwarding the request to the LLM and handling retries if the forwarded request fails
Alban
·
·
Hi, do you use the 'blocking=true' parameter?
Alban
·
·
If you don't, then the answer will be streamed and you'll have to catch the streaming events
Alban
·
·
https://docs.dust.tt/reference/get_api-v1-w-wid-assistant-conversations-cid-events
Nicolas Boussenina
·
·
For creating the convo yes 😄 But then I'm sending messages with https://docs.dust.tt/reference/post_api-v1-w-wid-assistant-conversations-cid-messages and there is no such 'blocking' parameter for this endpoint
Alban
·
·
Ha yes, if you are inside a conversation you have to go through the streaming events