This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have a test github repo set up with an azure automation account using source control. The source control sync job ran successfully twice on 26th Apr 2024, but now fails.
There is no error given in the summary in the azure portal, the "all logs" page just shows the following:
Waiting for job output..
When querying the sync job using PowerShell, I receive the following:
Exception : Job Failed. An unhandled exception occurred.
ResourceGroupName : redacted
SourceControlName : redacted
AutomationAccountName : redacted
SourceControlSyncJobId : redacted
ProvisioningState : Failed
SyncType : FullSync
StartTime : 5/6/2024 7:31:49 PM +01:00
EndTime : 5/6/2024 7:31:49 PM +01:00
CreationTime : 5/6/2024 7:28:39 PM +01:00
I have tried the same repo, and a separate repo hosted in github, and in azure devops, in a separate azure automation account in a separate tenant. I see exactly the same behaviour in all circumstances.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 79%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDW%3C/text%3E%3C/svg%3E)
I don't have an answer/solution - just adding my voice.
I'm seeing the same behavior. Multiple Automation Accounts, multiple Azure DevOps repos. As far as I can tell it started this morning (I had a successful sync last week). The sync job queues for 4 minutes (that has been very consistent) and then returns as failed. There is no error and the output is simply "Waiting for job output..."
Exactly the same issue here... this started happening earlier today. Have tried removing and re-adding the source control but it doesnt do the trick!
It seems to be sorted now. This is the response I got from MS Support:
"Our product team has been migrating source control jobs to new ACI environment. They have identified the backend service issue and already reverted back after detecting the issue."
I did run another full sync now to confirm this.
Good luck!
Looks like it is resolved for me, successful full sync this morning :)