In our application, we different interaction driver categories(Bankruptcy, Account Handling) and each of them has its own data source and intent tasks. Our business users reported that when the user selects a intent task in the category "Bankruptcy" and submit it in the driver, it starts the flow of the task corresponding to the other category "Account Handling" instead of the expected task.
This is happening intermittently. We are not able to reproduce this issue in lower environment.
This happened for many users in this week. This was not reported before.
We are not able to identify what could be the reason. Appreciate your help on this to analyze and finding the root cause.
Please let me know if you need any additional information.
In a perfect world you'd get a trace of this. It's not clear why that would be happening. Presumably, the primary page is of the wrong class. Without knowing your custom code, I don't know why that would be. Do you have any users who see this more often than others? Could you put Fiddler on their desktop and set it to capture the last 500 interactions (or whatever number seems reasonable) and have them save the trace off when the problem occurs? That way will get a good look at the exact request that results in the issue.
If you post the small excerpt of code that actually makes the decision regarding which category flow to run, we may be able to suggest what kind of diagnostic you should insert for understanding better why the issue is occurring. /Eric