pm.execution.setNextRequest('ID') causing collection to end rather than route to ID'd request in manual collection runner

[danny-dainton]

Hey @romeatcareqb

What is the response body of the first request?

Are you sure that the condition is met as expected, are you able to log that out to the console?

Are you using the request name of the id of the request, inside the setNextRequest() method?

What do you mean by manual collection runner, are you just referring to running the Collection using the runner or manually hitting send on the requests?

Is this the same question as you raise here?

Issues with pm.execution.setNextRequest() inside the manual collection runner

I am trying to use some conditional routing to skip a request in a collection based on whether certain variables are present earlier in the sequence. In the post-request script, we check for the presence of the variable, and then very simply either route to the next request in the sequence or the n+1 request. For some reason, when I run this in the manual collection runner, the runner just stops after the request containing the conditional routing, and I can’t figure out why. If I comment out t…