Two times in the last two days the locationsRoot node was left unpublished because we were seeing 404 not found. The only operation on it is the one above as nobody is manually entering the backend at the moment.
Checking the logs I don't see anything regarding this, in fact all the logs indicate that the publish was successful.
Has anyone seen something like this and does anyone have any ideas on how to troubleshoot it?
Version 8.9 on azure web app setup with appropriate configs and we aren't scaling out so it is just one instance.
ContentService.SaveAndPublishBranch sometimes leaves the Node unpublished
We have a site that runs a sync to another system every 30 minutes. It is location data:
The individual locations save/sync and then I call:
_contentService.SaveAndPublishBranch(locationsRoot, false);Two times in the last two days the locationsRoot node was left unpublished because we were seeing 404 not found. The only operation on it is the one above as nobody is manually entering the backend at the moment.
Checking the logs I don't see anything regarding this, in fact all the logs indicate that the publish was successful.
Has anyone seen something like this and does anyone have any ideas on how to troubleshoot it?
Version 8.9 on azure web app setup with appropriate configs and we aren't scaling out so it is just one instance.
is working on a reply...