I'm working with an Azure Function App that contains multiple functions. By mistake, I deployed a new function with a name that already existed in the project. After fixing this, the Azure Portal failed to update the function list, and every deployment attempt failed at the Kudu-SyncTriggerStep with an error.I tried the following to resolve the issue, but none worked: Manually triggering synchronization in the Azure Portal. Running the sync command via the Azure CLI. Deleting the deployment files in the associated storage account. Publishing a new project with a single function to overwrite the existing configuration.
In the end, I had to recreate the Azure Function App resource and redeploy with a corrected function name. Has anyone encountered this issue before? Is there a better way to resolve this without recreating the entire resource?
Yes, this happens sometimes with Azure Functions. When two functions with the same name exist, the metadata in the storage account and the function app’s host.json/config get messed up. Once that happens, the portal and Kudu struggle to reconcile the function list, which is why deployments and sync triggers start failing.
Unfortunately, there isn’t always a clean “one-click” fix. The usual tricks—manual sync, CLI sync, clearing deployment files, or redeploying a smaller project—often don’t work because the corrupted metadata doesn’t get fully reset. That’s why recreating the Function App worked for you: it gave you a fresh state.
A couple of slightly less destructive things you could try next time before recreating the whole app:
Delete the broken function explicitly: Remove the function folder from wwwroot (via Kudu or FTP) and check that it’s gone from the storage account under AzureWebJobsStorage.
Stop → Deploy → Start: Sometimes stopping the Function App before deploying the corrected version lets it reset properly.
Use slots: If you deploy into a staging slot, you can blow away and redeploy that slot without affecting production, then swap once it’s good.