I'm encountering an issue with my tumbling window trigger configuration, and I'm hoping someone can provide insights or advice. My trigger is defined as follows:

    },
    "type": "TumblingWindowTrigger",
    "typeProperties": {
        "frequency": "Minute",
        "interval": 30,
        "startTime": "2025-02-04T12:00:00Z",
        "delay": "00:00:00",
        "maxConcurrency": 1,
        "retryPolicy": {
            "count": 3,
            "intervalInSeconds": 30
        },
        "dependsOn": [
            {
                "type": "SelfDependencyTumblingWindowTriggerReference",
                "offset": "-0.00:30:00"
            }

In my pipeline, I have a Databricks activity followed by a Power BI refresh activity. Additionally, I've implemented an artificial waiting time as described in a blog post I came across.

This setup was functioning well for some time, but I recently encountered an incident where I had to cancel a pipeline run and restart it. After re-running the canceled pipeline, it succeeded, but the subsequent run is now stuck in a "waiting on dependency" state. Previously, re-running a failed run would resolve such issues, but that doesn't seem to be the case this time.

• Does anyone have insights into what might be causing this problem?
• Could the mandatory backfill mechanism be the root cause of the dependency issue I'm experiencing? I can not find any documentation regarding that.

I'm really in a tough spot having to manually monitor and trigger this pipeline now.

Update documentation explicitly states "TW trigger can not be cancelled while being in wait on dependency state"