Description
Inbound emails are not creating new conversations in our QuackBack deployment.
When an inbound email is received through the email integration, QuackBack responds with:
{
"status": "no_conversation"
}
However, the main QuackBack Docker image correctly creates a new conversation when processing the same type of inbound email.
This suggests a difference in the email ingestion/conversation-creation logic between the deployed image/version and the main image.
Expected behavior
When an inbound email is received, and there is no existing conversation matching the email/thread, QuackBack should create a new conversation in the configured workspace/inbox and associate the inbound email with it.
Description
Inbound emails are not creating new conversations in our QuackBack deployment.
When an inbound email is received through the email integration, QuackBack responds with:
{
"status": "no_conversation"
}
However, the main QuackBack Docker image correctly creates a new conversation when processing the same type of inbound email.
This suggests a difference in the email ingestion/conversation-creation logic between the deployed image/version and the main image.
Expected behavior
When an inbound email is received, and there is no existing conversation matching the email/thread, QuackBack should create a new conversation in the configured workspace/inbox and associate the inbound email with it.