You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Usync version 4.0.16
Umbraco 7.15.6
Azure Web Apps
I have a pipeline in Azure Devops with several stages (dev, uat etc). Usync is enabled with auto import on startup (usync content not enabled).
The issue is that new fields are not always imported, even though other changes such as new data types are imported correctly.
The strange thing is that when this happens, it is usually only on one or two stages in the pipeline, but in other stages it works. The ones that fail are not always the same ones, so one time it might fail on dev but work on uat, other times it's the other way round. All the web apps are configured the same, and the same app is deployed to each one.
There are no error messages in the log.
Any ideas what might be causing this or how to go about debugging?
The text was updated successfully, but these errors were encountered:
:( - no real ideas on what might be causing that - but you could turn on the debug logging - adding the below to log4net.config file should give you more info. to look at when it fails.
Usync version 4.0.16
Umbraco 7.15.6
Azure Web Apps
I have a pipeline in Azure Devops with several stages (dev, uat etc). Usync is enabled with auto import on startup (usync content not enabled).
The issue is that new fields are not always imported, even though other changes such as new data types are imported correctly.
The strange thing is that when this happens, it is usually only on one or two stages in the pipeline, but in other stages it works. The ones that fail are not always the same ones, so one time it might fail on dev but work on uat, other times it's the other way round. All the web apps are configured the same, and the same app is deployed to each one.
There are no error messages in the log.
Any ideas what might be causing this or how to go about debugging?
The text was updated successfully, but these errors were encountered: