Since the start of September 2025 people started getting issues when trying to run a database sync while deploying models on UDE DEV environments, as can be seen in this Yammer thread.
Specifically, the following error message is displayed, seemingly unrelated to the models being deployed/synced:
Error Message: "Microsoft.Dynamics.CAP.Iris.Connectors.Exceptions.DSSidecarOperationException: DS/Sidecar operation: dbsync failed with the error code FailedDependency; error message: Failure happened while running DBSync on environment fosandbox16..\r\n\tstatusCode = FailedDependency\r\n\r\n at Microsoft.Dynamics.CAP.Iris.Jobs.LifecycleJobs.DBSyncJob.RunPollAsync(DBSyncMetadata dbsyncMetadata) in C:\\__w\\1\\s\\src\\Iris.Infrastructure\\Jobs\\Lifecycle\\JobCallbacks\\CommonActions\\DBSyncJob.cs:line 108\r\n at Microsoft.Dynamics.CAP.Iris.Jobs.Platform.LongRunningWithPollingJob`1.RunAsync() in C:\\__w\\1\\s\\src\\Iris.Infrastructure\\Jobs\\Platform\\LongRunningWithPollingJob.cs:line 60\r\n at Microsoft.Dynamics.CAP.Iris.Jobs.Platform.WhatIfModeSupportedJob`1.ExecuteAsync() in C:\\__w\\1\\s\\src\\Iris.Infrastructure\\Jobs\\Platform\\WhatIfModeSupportedJob.cs:line 68"
The fix
Luckily, the fix is pretty easy.
Instead of syncing when deploying the models to the UDE environment, just do the following:
First deploy just the code of the models you are updating:
Hello, I have been running into this issue and tried this solution. I still seem to be receiving the same error message after just doing a deployment (no DB sync), do you know if there are any other config/build settings that could be causing the same error message to occur?
For me, the issue was happening only on the sync part, and isolating the model deployment from the dbsync seemed to fix it.
I’m not sure if there is maybe some setting in Visual Studio that is doing the sync automatically, even if you don’t explicitly sync when deploying.
My only idea is that maybe you could try doing a full sync first, then try to deploy the models only? Hopefully that will help.
From what I saw on Yammer (this post and this post), people were able to solve it by doing the full sync separately.
One of the other proposed workarounds on Yammer was to: “…add the specific field in the Project and Right click the project and Sync Database - This will execute db sync of specific table only on that project.”
If that doesn’t work either, I encourage you to join the conversation on Yammer and hopefully someone had the same issue and has a fix.
I did try doing the DB sync first and then deploying, although that unfortunately didn’t seem to change anything. I also don’t think our company has a license for Yammer, so I am unable to see those posts as of now. My scenario is that I am trying to deploy some custom models that we had previously set up on devbox VMs, so it’s a little hard to narrow down specific fields since we have some pre-existing projects already. I’ll take a look some more at the settings to see if I can find anything, but I’m glad to know that I am not the only one having this problem.
