Removed trigger still triggers

Question

Removed trigger still triggers

Anonymous

Hi!

I had a trigger in Azure Data Factory with a related pipeline. The trigger has been deleted (and the change published) but it is still triggering over 12 hours later.
The trigger is not in the GUI, not connected to the pipeline and not in Git.

What can I do? Is something cached somewhere?

Best regards

Smaran Thoomu 24,260 Reputation points Microsoft External Staff Moderator

2025-02-19T15:59:46.3033333+00:00
Hi @JE
I'm sorry to hear you're experiencing this issue. Let's work together to resolve it. Here are some steps you can take:

Ensure that after deleting the trigger, you clicked Publish in Azure Data Factory. Without publishing, changes won't take effect, and the trigger may continue to run.

Navigate to the Monitor section in Azure Data Factory and look for any ongoing or scheduled runs associated with the deleted trigger. If found, manually stop them to prevent further executions.

Sometimes, a simple restart can clear residual processes. Restart your Azure Data Factory instance to ensure all settings are refreshed.

Verify that no other triggers are inadvertently set to activate the same pipeline. It's possible another trigger is causing the pipeline to run.

Occasionally, the interface might not reflect recent changes due to caching. Clear your browser cache or try accessing Azure Data Factory from a different browser to see if the issue persists.

If after these steps the problem continues, it might be a deeper issue. Please let us know if this not solves.
Smaran Thoomu 24,260 Reputation points Microsoft External Staff Moderator

2025-02-20T11:02:36.54+00:00

@JE We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Anonymous

2025-02-21T08:32:26.64+00:00
Hi @Smaran Thoomu ,

Thanks for the response.

I have clicked Publish after deleting the trigger.

On the monitor section I can see when the deleted trigger is triggering the pipeline (once a day). It fails instantly with error: "Execution failed due to throttling or concurrency issues and TriggerContext {Trigger} does not have any property, please retry later."

Is it actually possible to restart Azure Data Factory - how?

There is another trigger that triggers the same pipeline successfully - and this is correct.

I've tried this but the trigger is still not visible.
Smaran Thoomu 24,260 Reputation points Microsoft External Staff Moderator

2025-02-21T12:59:04.6633333+00:00
Hi @JE
Thanks for sharing the update! Since you’ve already published the changes and confirmed that the deleted trigger is still running, here are a few more things you can try:

Since the deleted trigger is still appearing in the Monitor section, it might be a cached execution. Try manually stopping any running or queued runs related to this trigger.

Sometimes, the UI doesn’t fully reflect changes. You can use Azure Data Factory REST API to list all triggers and confirm whether the deleted one is still registered.

Run this command in Azure CLI:
az datafactory trigger list --resource-group <your-rg> --factory-name <your-adf-name>
If the trigger still appears, you may need to delete it via API.

ADF itself doesn’t have a "restart" option like virtual machines, but you can try stopping and restarting the Integration Runtime (if using a Self-Hosted IR).

Navigate to Azure Data Factory > Manage > Integration Runtimes, then stop and restart your IR.

Since the error mentions throttling/concurrency issues, it’s possible that ADF is holding onto a stale trigger reference. If the issue persists, you may need to open a support ticket with Azure to clear any backend inconsistencies.

I hope this information helps. Please do let us know if you have any further queries.
Anonymous

2025-02-24T10:51:04.33+00:00
Hi @Smaran Thoomu ,

Thanks for the support.

There doesn't seem to be a cached execution. The deleted trigger is executing one new pipeline run at the same time every day - and the execution always fails in less than one second (and does not continue to run).

I tried to run:

az datafactory trigger list --resource-group <your-rg> --factory-name <your-adf-name>

But the deleted trigger does not appear.

I don't have a self-hosted integration runtime, so can't try that..
Smaran Thoomu 24,260 Reputation points Microsoft External Staff Moderator

2025-02-25T11:23:37.57+00:00

@JE Could you please check the private message I sent you?

Your answer

Smaran Thoomu 24,260 Reputation points Microsoft External Staff Moderator

2025-02-19T15:59:46.3033333+00:00

Hi @JE
I'm sorry to hear you're experiencing this issue. Let's work together to resolve it. Here are some steps you can take:

Ensure that after deleting the trigger, you clicked Publish in Azure Data Factory. Without publishing, changes won't take effect, and the trigger may continue to run.

Navigate to the Monitor section in Azure Data Factory and look for any ongoing or scheduled runs associated with the deleted trigger. If found, manually stop them to prevent further executions.

Sometimes, a simple restart can clear residual processes. Restart your Azure Data Factory instance to ensure all settings are refreshed.

Verify that no other triggers are inadvertently set to activate the same pipeline. It's possible another trigger is causing the pipeline to run.

Occasionally, the interface might not reflect recent changes due to caching. Clear your browser cache or try accessing Azure Data Factory from a different browser to see if the issue persists.

If after these steps the problem continues, it might be a deeper issue. Please let us know if this not solves.
Smaran Thoomu 24,260 Reputation points Microsoft External Staff Moderator

2025-02-20T11:02:36.54+00:00

@JE We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Anonymous

2025-02-21T08:32:26.64+00:00

Hi @Smaran Thoomu ,

Thanks for the response.

I have clicked Publish after deleting the trigger.

On the monitor section I can see when the deleted trigger is triggering the pipeline (once a day). It fails instantly with error: "Execution failed due to throttling or concurrency issues and TriggerContext {Trigger} does not have any property, please retry later."

Is it actually possible to restart Azure Data Factory - how?

There is another trigger that triggers the same pipeline successfully - and this is correct.

I've tried this but the trigger is still not visible.
Smaran Thoomu 24,260 Reputation points Microsoft External Staff Moderator

2025-02-21T12:59:04.6633333+00:00

Hi @JE
Thanks for sharing the update! Since you’ve already published the changes and confirmed that the deleted trigger is still running, here are a few more things you can try:

Since the deleted trigger is still appearing in the Monitor section, it might be a cached execution. Try manually stopping any running or queued runs related to this trigger.

Sometimes, the UI doesn’t fully reflect changes. You can use Azure Data Factory REST API to list all triggers and confirm whether the deleted one is still registered.

Run this command in Azure CLI:
az datafactory trigger list --resource-group <your-rg> --factory-name <your-adf-name>
If the trigger still appears, you may need to delete it via API.

ADF itself doesn’t have a "restart" option like virtual machines, but you can try stopping and restarting the Integration Runtime (if using a Self-Hosted IR).

Navigate to Azure Data Factory > Manage > Integration Runtimes, then stop and restart your IR.

Since the error mentions throttling/concurrency issues, it’s possible that ADF is holding onto a stale trigger reference. If the issue persists, you may need to open a support ticket with Azure to clear any backend inconsistencies.

I hope this information helps. Please do let us know if you have any further queries.
Anonymous

2025-02-24T10:51:04.33+00:00

Hi @Smaran Thoomu ,

Thanks for the support.

There doesn't seem to be a cached execution. The deleted trigger is executing one new pipeline run at the same time every day - and the execution always fails in less than one second (and does not continue to run).

I tried to run:

az datafactory trigger list --resource-group <your-rg> --factory-name <your-adf-name>

But the deleted trigger does not appear.

I don't have a self-hosted integration runtime, so can't try that..
Smaran Thoomu 24,260 Reputation points Microsoft External Staff Moderator

2025-02-25T11:23:37.57+00:00

@JE Could you please check the private message I sent you?

Share via

Removed trigger still triggers

Your answer