[Bug] Update Message Status 401 With Custom Conversation Provider

[i-am-rad]

🐛 Describe the Bug

1. Create a default SMS provider (not marked as custom)
2. Send outbound message
3. Immediately try to update the message status to delivered.
4. Returns 401: "No conversation provider found for this message"
5. Your database updates at some point 5 to 10 seconds later.
6. We update message status again with same payload and it does update the message.

📍 Location

https://marketplace.gohighlevel.com/docs/ghl/conversations/update-message-status

✅ Expected Behavior

200 - message updated

💻 Screenshots or Code Samples

N/A

🧠 Additional Context

Conversations team is tracking

[andrewcezar]

Having the exact same issue! Any updates?

[i-am-rad]

I believe its resolved.

[balaji-ghl]

@i-am-rad Updated the failure status code from 401 to 403 as status changes are not allowed until the message is downstreamed to the conversation provider.

[i-am-rad]

Thats a start so we dont try to token refresh. Why can't you just queue our update message status actions to handle that downstream issue? Thats not good for fast 2 way messaging services to hold our CPU open longer for an unknown amount of time to update the message status. I timed it a few times and it took you guys like 5 to 10 seconds and sometimes longer. So its forcing a lot of retries on your endpoint. Just accept the payload on your end for custom providers and queue it up.

[i-am-rad]

Perspective is i have 3x retries with 3 seconds in between. 9 seconds of extra cpu time. And it has failed numerous times even with that.

[i-am-rad]

@balaji-ghl please update docs to reflect the new 403 error code

[balaji-ghl]

@i-am-rad Doc changes are already planned and will be rolled out in the next release. Since this isn't a blocker, I'm closing the issue. Feel free to reply in this thread to reopen it or create a new one if you have any questions or concerns.