Azure Data Factory: The pipeline does not start with Trigger now , but same pipeline starts and runs with Debug

Sunita Gannavarapu 66 Reputation points Microsoft Employee
2023-10-06T11:15:21.8133333+00:00

Hi Team, I am facing issue. The pipeline started when I used debug and ran fine. But when I use trigger now to run the pipeline it fails saying

{"code":"BadRequest","message":"Invalid value for property 'parameters'","target":"pipeline/ExportCSVPipeline/runid/771c435e-26eb-47c6-89d0-8f28e361b47a","details":null

I provided the same value for the parameter when running via Debug.

did a publish and tested but same result. Verified the Json(input parameter value) and its valid Json.

This issue is similar to the issue mentioned in : https://learn.microsoft.com/en-us/answers/questions/107357/azure-data-factory-trigger-is-fired-but-pipeline-d?page=1&orderby=Helpful&comment=answer-119031#newest-answer-comment

Can you elaborate what action was taken to solve the issue ?

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
9,753 questions
{count} votes

Accepted answer
  1. KranthiPakala-MSFT 46,427 Reputation points Microsoft Employee
    2023-11-01T16:49:45.42+00:00

    @Sunita Gannavarapu I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others Opens in new window or tab", I'll repost your solution in case you'd like to accept the answer Opens in new window or tab.

    Error Message:

    • {"code":"BadRequest","message":"Invalid value for property 'parameters'","target":"pipeline/ExportCSVPipeline/runid/771c435e-26eb-47c6-89d0-8f28e361b47a","details":null

    Issue:

    • The pipeline does not start with Trigger now , but same pipeline starts and runs with Debug

    Solution:

    • Looks like Team made change in 1 of the linked service paramter. They changed it from hardcoded to a dynamic parameter receivable from data source. While making it dynamic, the value was specified in the ARM(JSON) but parameter name was not. This got deployed. and then it started breaking. Not a deployed issue though more of a coding error.

    If I missed anything please let me know and I'd be happy to add it to my answer, or feel free to comment below with any additional information.

    I hope this helps!

    If you have any other questions, please let me know. Thank you again for your time and patience throughout this issue.


    Please don’t forget to Accept Answer and Yes for "was this answer helpful" wherever the information provided helps you, this can be beneficial to other community members.

    1 person found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful