It looks like the dynatrace synthetic script does not keep cookie's an values between steps. I have noticed that you can define cookies using an event. It would be nice if the value from a previous step could be used here.
In first steps I login, a session cookie is used. And after the login in the next step a 400 (deceptive) request is send back. I mimicked this by removing the session cookie in the browser.
Solved! Go to Solution.
For Browser Monitors, I wouldn't expect this to occur, once a Cookie is set I would expect it to persist for that execution.
For HTTP Monitors, I would expect the cookie to need to be set with each request and this can be done by pulling the session id and then adding it into the subsequent requests. There's a similar example in the docs here.
If this is for a Browser Monitor, can you create a Support ticket for Dynatrace to investigate?