Preventing ContentEvents when running scheduled job.

Mattias Brage

Vote:

I have a question regarding Content Events and/or scheduled jobs in relation to the "Change log" tool in Optimizely.

The situation is as follows: I have a scheduled job that creates and edits many pages of the content types OfficePage and ProfilePage. Since this job runs frequently, the "Change log" tool in Admin gets flooded with "Publish" events generated by the job.

The site administrators would like to exclude these events from the "Change log" so that they can more easily see the pages they have updated themselves.

I have tried setting CancelAction on the PublishedContent event, but it doesn’t seem to have any effect.

A solution that filters the Change log either by a specific user (the scheduled job user) or by specific content types would be fine. Alternatively, a solution where the change events triggered by the scheduled job user are not logged at all would also work.

#340223

Sep 03, 2025 13:29

Quan Mai

Vote:

I would suggest to go with the former (filter by users) instead of the latter (not logging). Logging should be there regardless of who is doing the actions

#340252

Sep 05, 2025 7:32

Mattias Brage - Sep 05, 2025 7:40

Is it possible to change the "Change log" interface or do i need to create a separate GUI for it? As it is now you can only filter to view changes by a user, not filter out a specific user.

Quan Mai - Sep 05, 2025 8:16

There is currently no builtin filtering as you need, but I do agree that improvements to Change Log should be made. Feel free to vote this up https://feedback.optimizely.com/forums/966081-cms-paas-content-management-system/suggestions/50426301-change-log-filtering so it gets considered

Mark Stott

Vote:

I have a number of clients who use scheduled jobs to import data into the CMS. If you don't want to flood the version history or change log, then I would suggest making sure your scheduled job has some form of change validation. For example, calculate a checksum on the source data and validate it against a stored checksum against the target content item before deciding to make a change.

#340294

Sep 08, 2025 10:44

Mattias Brage - Sep 08, 2025 10:56

Thanks for the advice. We have some sort of validation in place, it's not like every page get a change every time. The changes that are made and reflected in the version history are in fact real changes. We ended up writing a custom tool using the IActivityQueryService.

Quan Mai - Sep 08, 2025 11:59

that's a smart workaround - did not think of it.