When a particular requests is run through the desktop app, individually or with the collection runner, it passes 100% of the time so far.
This same request, when run through a gitlab pipeline using postman-cli consistently fails with a 400 Bad Request error.
What might cause this dramatic difference in results for the same request?
Postman-cli version is: 1.19.4
Welcome to the Postman Community! 
Could you share any other details about the failing requests, their structure or payloads? Do these use any variables that might not be resolved in the pipeline run?
What does the Gitlab workflow file look like and the Postman CLI command?
The more details that you can share will make things eaiser to get to the root of the problem 
1 Like
Hi Danny Thank you for your response! I’m adding information below, please let me know if this doesn’t help or isn’t enough. 
I ran with the verbose flag turned on and it looks like when run in the pipeline, the userID isn’t being parsed, though the desktop app does show the variable resolving.
This is a screenshot of what the gitlab pipeline returns:
This is a screenshot of what the postman console shows when running the same exact request:
Found the cause: the request that sets that variable somehow lost the script to set it. Not sure how or when that happened, but adding that script back in fixed my fails. Thank you!
1 Like