Forum Discussion
7 Replies
Hi SagarShroff,
This could be due to many things. The likely issue, in my opinion, is related to correlation. That is, there are probably some session-related values in your scenario that are dynamic and need to be unique for each user. If this is true in your case, it could mean that the server receives those recorded values and redirects or returns an error.
The process of correlation in LoadComplete is described here. If you would like help looking at your scenario, please contact me at ryan.heidorn@smartbear.com and I would be happy to provide assistance.
Best,
- SagarShroffOccasional Contributor
I had verified that i am sending correct dynamic tokens in subsequent request. As i mentioned earlier it was working via 'Verify Scenario' but was failing when i run it via test.
Anyways i got it working, after environment restart. But dint understood the behaviour. Thanks for the reply.
- SagarShroffOccasional Contributor
So the solution was, there is a global settings under logging to store full headers and bodies. And it was the default settings. The main problem is that it was logging both headers and bodies in 'Verify Scenario' but when executed via tests then it was logging as per configuration which led to confusion. Please fix it.