Log scheduling (at least for internal use!) (Better logging of scheduled publish/unpublish successes and failures) [Edited title]

[codestuff]

We recently had a singleton record unpublished at midnight. It should have published new content - that was the plan. This lead to our start page showing an “Oops, we messed up” for 6 hours until someone from our team went onto the record the next morning and pressed “Publish”.

The most likely culprit is human error: choosing to unpublish instead of publish the record at midnight in the scheduling - and this is an easy mistake to make since it is a radio button choice without any confirmation or warning about the potential consequences.

When bringing this up with support, it was made clear to us that there is no logging of what was scheduled, when and by whom. This would have been very very helpful to track down the actual cause of this error. If not in the UI for me as a user, at least so that your support staff can access it!

(Also, wouldn’t an extra warning for an unpublishing operation be a warranted affordance? It can have grave consequences if it happens by mistake.)

TLDR: Log scheduling at least internally to make troubleshooting easier!

[roger]

Just dropping a note here that, for Enterprise customers, the Audit Log feature does track user-initiated changes to the scheduled publishing (i.e. when you create or remove a scheduled publishing event):

However, it still does not track the actual success/failure of the event (which is what the OP asked for). It’s useful for tracking “who changed the schedule”, but not necessarily “did it publish successfully”.