Jean Langlois-Meurinne

Commented on Need Help with Script for Dust SSE Conversation Ma...·Posted inHelp

Thanks, it works even if sometimes there is a timeout before any complete answer is received (even with very long response time). I’ll try to work it out and tell you if it doesn’t

Commented on Need Help with Script for Dust SSE Conversation Ma...·Posted inHelp

Voici le fichier sur lequel j’ai travaillé pour l’instant mais tout modèle qui réalise ces fonctions de base serait utile pour que je comprenne bien le fonctionnement des flux SSE

Commented on Need Help with Script for Dust SSE Conversation Ma...·Posted inHelp

Jean Langlois-Meurinne

Posted in Help·

Jean Langlois-Meurinne

Need Help with Script for Dust SSE Conversation Management?

Hello everyone, does anyone have a standard script to create a conversation, send a message, listen for agent response and retrieve it ? I’ve been trying to create such a script without success and having difficulty understanding how Dust SSE works.

5Comments

Commented on API Issue: Conversation Not Found Error After Crea...·Posted inHelp

Jean Langlois-Meurinne

Oh yes, you’re right, it should work. Let me try.

Commented on API Issue: Conversation Not Found Error After Crea...·Posted inHelp

Jean Langlois-Meurinne

Pardon pour le formatage, je ne connais pas bien les balises Slack

Commented on API Issue: Conversation Not Found Error After Crea...·Posted inHelp

Jean Langlois-Meurinne

Voici l’URL URL: https://dust.tt/api/v1/w/workspaceID/assistant/conversations/5187110/messages (avec l’ID correspondant à mon espace) Voici le body { "content": "Et qu’a-t-elle inspiré ensuite ?", "mentions": [ { "configurationId": "FIqVf0rjz9" } ], "context": { "username": "jean", "origin": "api", "timezone": "Europe/Paris" } } Et voici la réponse {"error":{"type":"conversation_not_found","message":"Cannot access conversation: conversation_not_found"}}

Commented on API Issue: Conversation Not Found Error After Crea...·Posted inHelp

Jean Langlois-Meurinne

I’ve tried to do :

1, Conversation with message with blocking = true (it works)
2. Create message within the conversation (it says impossible to retrieve conversation)
3. Get events in the conversation (doesn’t get to that stage)

I still have a problem accessing a conversation that is supposed to be existing. My problem is that I cannot handle multiple step discussions.

Commented on API Issue: Conversation Not Found Error After Crea...·Posted inHelp

Jean Langlois-Meurinne

Let me try again that option and tell you if it works. Initially I tried it but i had trouble creating messages in the same conversation, it seemed like i had to create new conversations each time. Maybe there was a wrong API call

Posted in Help·

Jean Langlois-Meurinne

API Issue: Conversation Not Found Error After Creation

Subject: Unable to send a message immediately after creating a conversation (`conversation_not_found`) Hello, I’m experiencing a consistent issue with the API `POST /assistant/conversations/{cid}/messages` immediately after creating a conversation using `POST /assistant/conversations`. Integration context The service uses the Dust API to serve messages from an AI agent. I’m using API key authentication on my workspace. The service creates a persistent conversation via: POST /v1/w/{wid}/assistant/conversations with the following body: { "title": "gpt4_username", "visibility": "unlisted" } Then, it immediately attempts (within <1s) to send a message with: POST /v1/w/{wid}/assistant/conversations/{cid}/messages with the following body: { "content": "Bonjour", "mentions": [{ "configurationId": "xxxxxxxx" }], "context": { "username": "@user", "origin": "api", "timezone": "Europe/Paris" } } Issue encountered Every time I try to send a message right after the conversation is created, I get the following error: { "error": { "type": "conversation_not_found", "message": "Cannot access conversation: conversation_not_found" } } However, the conversation creation returns `200 OK` with a valid ID (`cid`). The problem persists even after waiting several seconds and after multiple attempts. If I use `blocking: true` during conversation creation with an embedded message, everything works fine. Tested hypotheses

The `conversation_id` used is the one returned by the API (verified in logs).
The `agent_id`, mentions, headers, and context are all valid.
The conversation is correctly saved and reused (in database).
I also tested `GET /events` — same `404` issue.
The problem does *not* occur with `blocking = true`, but I’d like to manage messages separately.

Question

Is there an undocumented propagation delay between conversation creation and its availability for `POST /messages`?
Is there a recommended way to wait until the conversation is accessible and active on the API side?

My goal is to post messages to a persistent Dust conversation in order to better manage message history in the service’s responses — is there another recommended way to achieve this? Thanks in advance for your insights!

8Comments