In some edge cases, it is possible for agents to still create new translation requests when a conversation is no longer active. When this happens, Unbabel still receivers and processes the translation, but fails to deliver it to the session.

• the Unbabel chat component will list the message as failed
• the Translation Request associated with it will have a status for Request Failed, and an error reading "No active conversation for record"

Possible causes for this error include:

• the agent sent a message while offline in Omnichannel
• the agent lost the Omni-Channel messaging session and needs to accept the conversation again
• the customer ended the conversation before the agent sent the message

Our component may not be able or have some lag in detecting these changes compared to the native one, which can temporarily allow agents to request translations that will fail to deliver.

To minimize this risk, please ensure that you are correctly connected and the conversation is fully active when requesting a translation.