You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a near future, the workflow will also save the "response" messages by the chatbot in the same DynamoDB Table, making the workflow to look something like this:
So when the "answered messages" are added to the DynamoDB Table (kept with Single Table Design), it's important to avoid enabling the streams to be sent to the State Machine (as these are not user's messages, only the chat history...).
The proposed solution is to update the workflow to be:
Current workflow of the solution is implemented with:
In a near future, the workflow will also save the "response" messages by the chatbot in the same DynamoDB Table, making the workflow to look something like this:
So when the "answered messages" are added to the DynamoDB Table (kept with Single Table Design), it's important to avoid enabling the streams to be sent to the State Machine (as these are not user's messages, only the chat history...).
The proposed solution is to update the workflow to be:
With the correct
EventBridge Pipe
filter, the infinite loop can be avoided for the "answered responses" because of filtering the PK/SK.The text was updated successfully, but these errors were encountered: