18 May 2023
08:16 PM
- last edited on
29 May 2023
08:53 AM
by
MaciejNeumann
He is confusing the contexts of the requests. The error caused by Request A is being reported in Request B. We can see in the Error tab the stack shown in Request B is from Request A.
General timeline
Api B
- summary
- threads
- error
Api A
- Summary
- Threads
- Error
.net v6
Cluster AKS (azure)
Can anyone help me ?
Thanks,
15 Jun 2023 05:03 PM
is it because it part of the entire stacked trace and the two are dependent on eachother hence the error being present on both?
15 Jun 2023 05:16 PM
One request does not depend on the other but they are correlated because they come from the same client. The error that happens in context A is an unexpected and strange error, a TIMEOut exception is thrown but without a message. While in context B it is the expected error and message.
Is there any reason for this error confusion between contexts?