[Data Factory] Retry transient provisioning conflict on trigger start#33459
Draft
Copilot wants to merge 6 commits into
Draft
[Data Factory] Retry transient provisioning conflict on trigger start#33459Copilot wants to merge 6 commits into
Copilot wants to merge 6 commits into
Conversation
️✔️AzureCLI-FullTest
|
️✔️AzureCLI-BreakingChangeTest
|
microsoft-github-policy-service
Bot
requested review from
calvinhzy,
evelyn-ys and
yonzhan
Copilot
AI
changed the title
[WIP] Fix unable to start datafactory trigger using az cli
[Data Factory] Retry transient provisioning conflict on trigger start
May 28, 2026
Collaborator
|
Data Factory |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related command
az datafactory trigger start --factory-name <factory> --name "<trigger>" --resource-group <rg>Description
Starting a Data Factory trigger could fail with
400 BadRequest: Resource cannot be updated during provisioningwhen invoked during a short provisioning window.This change adds bounded retry handling for that specific transient condition in core SDK invocation flow.
Problem
az datafactory trigger startcan hit a transient provisioning conflict immediately after resource creation.Change
sdk_no_waitfor:400Resource cannot be updated during provisioning--no-waitpath remains non-retrying.Scope
azure-cli-coreso all commands using this shared path benefit from the same transient handling behavior.--no-wait,Testing Guide
az datafactory trigger start --factory-name <factory> --name "<trigger>" --resource-group <rg>--no-waitbehavior:az datafactory trigger start ... --no-waitdoes not enter retry flow.History Notes
[Data Factory]
az datafactory trigger start: Retry transientResource cannot be updated during provisioningfailures during trigger start.This checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.