A while ago I blogged about a use case where a pipeline fails during debugging with a BadRequest error, even though it validates successfully. If you’re wondering, this is the helpful error message that you get:
In that blog post, the issue was that there were some lingering user properties that were configured incorrectly and removing them (or fixing them) resolved the issue. Yesterday, I had the same error again in another pipeline, but I couldn’t find anything wrong with the pipeline and its activities (and yet again, validation didn’t return any errors). So I started removing activities one by one and starting the pipeline over and over to find the culprit.
Turns out, the offending activity was an Execute Pipeline activity. In that child pipeline, there was an issue with an expression (not a syntax error, but rather referencing an output of an activity that couldn’t be referenced). Fixing that expression resolved the BadRequest error in the parent pipeline. Conclusion: when you have a BadRequest situation on your hand, check the pipeline for broken expressions/references, but also any child pipelines.
------------------------------------------------
Do you like this blog post? You can thank me by buying me a beer 🙂
