Issue with AI Auto-Fill Data Overlap
Hi @BuildShip team,
I am using the OpenAI Assistant node with a tool that makes an API POST request to save the name, email, and phone number of the user. The name, email, and phone number are all auto-filled by the AI. While this functionality generally works well for collecting this information during conversations with users, I have encountered an issue.
I have attached a screenshot as an example.
On the left side of the screenshot, I tested this workflow as John Doe. The AI successfully collected and saved the name, email, and phone number during the conversation using the 'Update Contact' tool. Everything seemed to be functioning correctly for this test run.
However, in a subsequent test, I used the workflow as Jane Doe. As shown on the right side of the screenshot, after providing the name Jane, the AI used the 'Update Contact' tool to save the name in our CRM. Unfortunately, it also saved the previous test run's information for John Doe. This should not have occurred, as these were completely separate instances run in different incognito browser windows. The thread IDs for each contact are different, indicating that the AI does not remember previous conversations, but for some reason, the AI auto-fill retained and used the information from John Doe’s session.
This is a significant issue because our CRM automatically merges contacts with the same email or phone number, which means that contacts collected by the AI could be incorrectly merged, even if they originate from different instances. I am concerned about how the AI auto-fill retains information from separate thread IDs.
Could you please advise on how to resolve this issue? It is critical for us to ensure that the system is robust, especially given the high volume of traffic we expect.
P.S. I already sent a support ticket but wanted to share this here for anyone experiencing the same issue.
I am using the OpenAI Assistant node with a tool that makes an API POST request to save the name, email, and phone number of the user. The name, email, and phone number are all auto-filled by the AI. While this functionality generally works well for collecting this information during conversations with users, I have encountered an issue.
I have attached a screenshot as an example.
On the left side of the screenshot, I tested this workflow as John Doe. The AI successfully collected and saved the name, email, and phone number during the conversation using the 'Update Contact' tool. Everything seemed to be functioning correctly for this test run.
However, in a subsequent test, I used the workflow as Jane Doe. As shown on the right side of the screenshot, after providing the name Jane, the AI used the 'Update Contact' tool to save the name in our CRM. Unfortunately, it also saved the previous test run's information for John Doe. This should not have occurred, as these were completely separate instances run in different incognito browser windows. The thread IDs for each contact are different, indicating that the AI does not remember previous conversations, but for some reason, the AI auto-fill retained and used the information from John Doe’s session.
This is a significant issue because our CRM automatically merges contacts with the same email or phone number, which means that contacts collected by the AI could be incorrectly merged, even if they originate from different instances. I am concerned about how the AI auto-fill retains information from separate thread IDs.
Could you please advise on how to resolve this issue? It is critical for us to ensure that the system is robust, especially given the high volume of traffic we expect.
P.S. I already sent a support ticket but wanted to share this here for anyone experiencing the same issue.
Solution
@Jrocks, On checking the recent and the previous logs (which shows the issue) of your shared workflow via support the newer logs shows the correct values and does not repeats, As for the new logs if you compare the request inputs - the request body
We have found an issue that in some of the previous executions it used previous test data and repeated the executions twice, we are looking into this and will add a fix.
For now as a workaround, could you please delete and add the Assistant node again and give a try, and ship it again, it should perhaps solve this issue. Let us know if it works and occurs again.
emailemailWe have found an issue that in some of the previous executions it used previous test data and repeated the executions twice, we are looking into this and will add a fix.
For now as a workaround, could you please delete and add the Assistant node again and give a try, and ship it again, it should perhaps solve this issue. Let us know if it works and occurs again.
