When attaching a tag to a conversation, they do not always appear in the conversation view. They do, however, appear against the conversation when retrieved via the API. What can I do to mitigate this and ensure the tag always shows in the conversation?
My workflow (simplified), using the node intercom client, is:
- await conversation creation
- await attachment of one or more tags
Intercom client always responds successfully, however, it appears there is some internal intercom mechanism to associate a tag with a conversation part, and that perhaps there is a race condition between the part becoming available and the tag being attached.
When I retrieve the conversation from the API, i can see that the tags are attached to the conversation.
