Request Chaining issue on cold start?
Bug
Chaining of mutations has worked fairly well, although there seems to be an issue when trying to invoke a mutation with dependencies when cold-starting Yaak. I have to go run the underlying dependent mutations first to achieve success, versus running the primary mutation.
I have a video that I don’t’ want to share here
Windows
Can you let me know if Beta 7 fixes this? https://github.com/mountain-loop/yaak/releases/tag/v2026.3.0-beta.7
Will take a look at this!
Hey Greg. I tested 2026.3.0-beta.9 and this seems to be fixed. But not quite sure if I understood @Steve’s issue, if it’s the same I have experienced:
Having
response.body.path(...)in anauthTokenvariable in my Base Environment which calls a login request to retrieve a new JWT token, and then reusing that extracted token in every request’sBearer Tokenfor authentication.That did not work before on cold start without explicitly firing the login request. Now it seems to work! Thx