ADF Pipeline using Global parameter fails when triggered but succeed when debugged

Question

I'm working with ADF, using global parameters, and facing the issue. It works fine if I debug the pipeline. But, if I trigger the pipeline (manual or scheduled), it fails saying the property doesn't exist and it shows the name of the global parameter I'm trying to use.

I also tried recreating the global parameter based on some suggestions I saw over google by Microsoft community only. But still doesn't help. Global parameter is such an important and frequently used element of ADF. I am hoping we have the solution in place. Do respond to this as soon as possible. Need the help urgently.

Answer 1

Hello 09251703,

Welcome to the Microsoft Q&A forum.

The issue is most likely due to a publishing issue. It seems that the global parameters were not published correctly.

Can you perform a pull request from your master/main branch and publish the changes to adf live?

A similar thread has been discussed here: [https://learn.microsoft.com/en-us/answers/questions/97868/adf-global-parameters-error-after-trigger-(debug-w](https://learn.microsoft.com/en-us/answers/questions/97868/adf-global-parameters-error-after-trigger-(debug-w)

I hope this helps.