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
Currently, when logging an event that occurs within a specific conversation state, it is often unclear which state the system is in at that moment. The ambiguity arises from referencing the state stored in memory solely through the intent keyword or state label, both of which may not be unique identifiers. A more effective solution would involve using the actual ID of the node in the metamodel, as this ensures a unique and unambiguous identification of the current state. This enhancement would improve the precision and reliability of event logging in our system and make it easier to reconstruct conversation paths from event data
The text was updated successfully, but these errors were encountered:
Currently, when logging an event that occurs within a specific conversation state, it is often unclear which state the system is in at that moment. The ambiguity arises from referencing the state stored in memory solely through the intent keyword or state label, both of which may not be unique identifiers. A more effective solution would involve using the actual ID of the node in the metamodel, as this ensures a unique and unambiguous identification of the current state. This enhancement would improve the precision and reliability of event logging in our system and make it easier to reconstruct conversation paths from event data
The text was updated successfully, but these errors were encountered: