Azure Data Factory Trigger scenarios with 'Pipeline not found' scenarios When Executing Multiple Triggers
I need help solving I've looked through the documentation and I'm still confused about Quick question that's been bugging me - I'm sure I'm missing something obvious here, but Hey everyone, I'm running into an issue that's driving me crazy... I'm working with an scenario with Azure Data Factory where I'm trying to run a pipeline using multiple triggers, but I consistently receive a 'Pipeline not found' behavior. I have verified that the pipeline exists and is published, yet it seems that only the first trigger works as expected. The other triggers return an behavior message stating that the pipeline could not be found. I attempted to delete and recreate the triggers, but the scenario continues. Here’s a snippet of the trigger configuration I’m using in JSON format: ```json { "name": "myTrigger", "properties": { "type": "Schedule", "typeProperties": { "recurrence": { "frequency": "Day", "interval": 1 } }, "pipelines": [ { "pipelineReference": { "referenceName": "myPipeline", "type": "PipelineReference" }, "parameters": { "param1": "value1" } } ] } } ``` I’m using Azure Data Factory version 2.0. I’ve also checked the permissions and ensured that the service principal has access to the Data Factory and the associated resources. Additionally, I validated that the trigger execution time aligns with the schedule, yet the question remains unsolved. It seems like a conflicting state due to multiple triggers trying to reference the same pipeline. Has anyone experienced this before? How can I resolve this scenario to allow all triggers to execute the same pipeline without running into the 'Pipeline not found' behavior? My development environment is Windows. I'm working on a service that needs to handle this. Any ideas what could be causing this? For context: I'm using Json on macOS. What am I doing wrong? Has anyone else encountered this? I'm on Ubuntu 20.04 using the latest version of Json.