Hi, in our test environment, unfortunately quite some requests are failing from time to time, due to timeouts, environment not being available, you-name-it, so I want to give that requests a retry, especially when running the collections in Jenkins via newman. So I came up with a bit of code, that…

As you said above it’s copy&paste but even though that’ line not the point :slight_smile: I’ve tried Newman CLI as well and it’s not help me. This one: -x, --suppress-exit-code for example just override exit code forwhole pipeline flow In my case i need yo use exit code override only if one of t…

[image] danny-dainton: @michal.robaszewski.j @michal.robaszewski.j can you advice please?

Hi, The variable Next_Request when using setNextRequest is crucial. When you Break the Linear execution you are in command. If you declare setNextRequest in script with null or empty value it will just stop execution when it hit that line using Newman. I don’t know if this is expected feature but …

As according to the Postman documentation workflows should work as is follows: If postman.setNextRequest() is absent in a request, the collection runner defaults to linear execution and moves to the next request So even with the postman.setNextRequest() is empty the next request executed and inde…

Does it give you a different result if you add postman.setNextRequest(Next_Request); to the 2 places that @michal.robaszewski.j has it in the script you copied. He authored that script so would have more context around the execution paths and why things are in there. This is also the incorrect way …

The script work as expected for both ways: postman.setNextRequest(Next_Request) postman.setNextRequest() and linear flow executed as well for both but Newman return exit code 1 once one of the retries attempts has been failed

Is there a reason or an error message to suggest why it fails. Did the script fail or the request fail? The exit code in itself doesn’t really give anyone any clues as to why it failed.

of course all the point of the retry mechanism is to overcome such issues as timeouts and hang up so in my case this timeouts

Hey Guys, the above retry logics work perfectly when running test as a Collection set. However if I run a test manually, it doesn’t execute the setNextRequest. Is there a way we could make this retry feature working even when manually running just that one test. For example I have two test cases, …

Retry a failing request

Help Hub

StanislavMasarsky (Stanislav) May 20, 2021, 1:09pm 21

At the end what I need to do just some how to make Newman to ignore retry failed once at least one of the attempts succeeded

Topic		Replies	Views
Unable to run the same request multiple times Help Hub newman-project , tests , variables , collections	9	6463	March 8, 2021
Help with creating a simple retry/exit mechanism for postman tests Help Hub tests	1	9711	May 23, 2019
Retry on etimedout Help Hub tests , collections	3	4790	October 13, 2021
How to execute only failed requests in a collection Help Hub collections	2	2830	January 4, 2023
Change Variable After a Failed Request, and Retry Using a Test Script Help Hub tests , variables	4	2762	March 25, 2020

Retry a failing request

Related topics