Why does my C# code keep failing with “Resource cannot be updated during provisioning” even after multiple retries and delays?

Question

Why does my C# code keep failing with “Resource cannot be updated during provisioning” even after multiple retries and delays?

Rifatul Islam 0

"error": { "code": "BadRequest", "message": "Resource cannot be updated during provisioning", "target": "orbitaxbdltdstorageventtrigger", "details": null }

code:

        int maxRetries = 2;

        int delaySeconds = 180;

        for (int i = 0; i < maxRetries; i++)

        {

            try

            {

                triggerResource = await dataFactory.GetDataFactoryTriggers().GetAsync(triggerName);

                Logger.Info($"OC|AzureService|StartTrigger : Trigger {triggerName} starting....");

                await triggerResource.Value.StartAsync(WaitUntil.Completed);

                Logger.Info($"OC|AzureService|StartTrigger : Trigger {triggerName} started successfully.");

                break; // Success! Exit the loop.

            }

            catch (Exception ex)

            {

                Logger.Error($"OC|AzureService|StartTrigger : Failed to start trigger {triggerName}-{ex.Message}");

                await Task.Delay(TimeSpan.FromSeconds(delaySeconds));

            }

        }

    }

0 comments

1 answer

Your answer

Answer 1

Divyesh Govaerdhanan 10,850 Volunteer Moderator

Hi Rifatul Islam,

Welcome to Microsoft Q&A,

The root cause here is that your retry loop is using a fixed time delay (180 seconds) without first checking whether the trigger has actually finished provisioning before attempting to start it again. The ADF trigger goes through an intermediate Provisioning state after being created, modified, or stopped, and calling StartAsync while it is in that state always returns this error, regardless of how long you wait.

The fix: poll the trigger's provisioning state before calling StartAsync

Instead of retrying blindly after a fixed delay, check that the trigger's ProvisioningState is Succeeded before attempting to start it.

triggerResource = await dataFactory.GetDataFactoryTriggers().GetAsync(triggerName); 

var provisioningState = triggerResource.Value.Data.Properties.ProvisioningState;

Your current code retries up to 2 times with 180-second delays, but it does not check whether the trigger is actually in a stable state before each attempt. If the trigger takes longer than 180 seconds to finish provisioning (which can happen for storage event triggers with large subscriber counts or during ADF backend updates), all retries will hit the same error. This is a known pattern, adding a wait between trigger operations avoids the error, but the wait duration needs to be long enough for provisioning to complete, and using a fixed delay is unreliable

Please Upvote and accept the answer if it helps!!

Rifatul Islam 0 Reputation points

2026-03-29T05:52:22+00:00

Hi **Divyesh Govaerdhanan,
**triggerResource.Value.Data.Properties does not contain a ProvisioningState property.
Rifatul Islam 0 Reputation points

2026-03-29T05:56:21.3266667+00:00

hi **Divyesh Govaerdhanan,
**Thank you for your suggestions.

I have tried all the recommended approaches, including adding a long delay after trigger creation and implementing multiple retries with a delay of more than 3 minutes.

From my observations in the Azure Portal, when I manually start the trigger, the associated Event Grid subscription takes approximately 2–3 minutes to complete provisioning. I can clearly see the provisioning status there.

During execution of my code:

Before calling StartAsync(), I manually verify in the Azure Portal that the Event Grid subscription provisioning state is Completed.

However, once StartAsync() is invoked, the provisioning state changes again to Updating/Creating (depending on whether it’s the first attempt or a retry).

This update process again takes around 2–3 minutes to complete in the backend.

The issue is that StartAsync() does not wait for this backend provisioning to complete. Instead, it throws the error:

"Resource cannot be updated during provisioning"

This happens even though the Event Grid subscription eventually completes successfully after a few minutes.

Because StartAsync() fails before provisioning completes, the trigger does not start. This behavior occurs consistently on every attempt.

So effectively, even when I ensure the Event Grid subscription is in a completed state before calling StartAsync(), invoking StartAsync() itself causes another backend update, and the method fails before that update finishes.

Could you please advise how to handle this scenario, where StartAsync() triggers a backend update and fails before the provisioning process completes?

Divyesh Govaerdhanan 10,850 Volunteer Moderator

Hi Rifatul Islam,

Data.Properties returns DataFactoryTriggerProperties which is an abstract base class, RuntimeState is not directly on it. You need to cast to the specific derived type. Since your trigger is a storage event trigger (DataFactoryBlobEventsTrigger).

Since StartAsync itself kicks off a backend Event Grid subscription update that takes 2-3 minutes, the right pattern is to call it once and then poll until the trigger reports Started

// Step 1: Call StartAsync once
triggerResource = await dataFactory.GetDataFactoryTriggers().GetAsync(triggerName);
await triggerResource.Value.StartAsync(WaitUntil.Completed);
Logger.Info($"StartAsync returned for {triggerName}, polling for Started state...");

// Step 2: Poll until RuntimeState == Started (up to ~7.5 minutes)
int maxAttempts = 30;
int intervalSeconds = 15;

for (int i = 0; i < maxAttempts; i++)
{
    var current = await dataFactory.GetDataFactoryTriggers().GetAsync(triggerName);

    string runtimeState = null;
    if (current.Value.Data.Properties is DataFactoryBlobEventsTrigger t)
        runtimeState = t.RuntimeState?.ToString();

    Logger.Info($"Trigger {triggerName} RuntimeState = {runtimeState} (poll {i + 1}/{maxAttempts})");

    if (runtimeState == "Started")
    {
        Logger.Info($"Trigger {triggerName} is now active.");
        return;
    }

    await Task.Delay(TimeSpan.FromSeconds(intervalSeconds));
}

This handles the exact scenario you described, where StartAsync triggers a new Event Grid update that takes time to complete on the backend. Hope this resolves it.

Share via

Why does my C# code keep failing with “Resource cannot be updated during provisioning” even after multiple retries and delays?

1 answer

Your answer