Incident Is updated by SystemIssue Some cases will create incidents that are updating the system but not showing in the transaction logs, not showing in the work notes or additional comments. The only thing we can see is an updated system and updated date. 2019-05-17 01:32:54 (961) worker.5 worker.5 txid=f823ced4db61 *** Start Background transaction - system, user: system2019-05-17 01:32:54 (964) worker.5 worker.5 txid=f823ced4db61 Starting: Flow Engine Event Handler.cf2c76f2db652300598718df4b9619f6, Trigger Type: Repeat, Priority: 100, Upgrade Safe: true, Repeat: 2 Seconds2019-05-17 01:32:54 (964) worker.5 worker.5 txid=f823ced4db61 Name: Flow Engine Event Handler2019-05-17 01:32:54 (977) worker.5 worker.5 txid=f823ced4db61 Completed: Flow Engine Event Handler in 0:00:00.010, next occurrence is 2019-05-17 03:32:552019-05-17 01:32:55 (012) worker.0 worker.0 txid=f823ced4db61 *** Start Background transaction - system, user: system2019-05-17 01:32:55 (027) worker.4 worker.4 txid=f823ced4db61 *** Start Background transaction - system, user: system2019-05-17 01:32:55 (029) worker.0 worker.0 txid=f823ced4db61 Starting: report view events process.0fb2c110871321004ebe19fa84e3ecf8, Trigger Type: Interval, Priority: 100, Upgrade Safe: false, Repeat: 5 Seconds2019-05-17 01:32:55 (029) worker.0 worker.0 txid=f823ced4db61 Name: report view events process2019-05-17 01:32:55 (034) worker.4 worker.4 txid=f823ced4db61 Starting: activity.monitor timer INC0858620.64b7ed58db25f30057d6164948961969, Trigger Type: Once, Priority: 100, Upgrade Safe: false, Repeat:2019-05-17 01:32:55 (034) worker.4 worker.4 txid=f823ced4db61 Name: activity.monitor timer INC08586202019-05-17 01:32:55 (040) worker.0 worker.0 txid=f823ced4db61 Completed: report view events process in 0:00:00.009, next occurrence is 2019-05-17 03:33:002019-05-17 01:32:55 (051) worker.6 worker.6 txid=f823ced4db61 *** Start Background transaction - system, user: system2019-05-17 01:32:55 (051) worker.4 worker.4 txid=f823ced4db61 Completed: activity.monitor timer INC0858620 in 0:00:00.014, next occurrence is nullCauseCheck the: Navigate to System Policy > SLA > Inactivity Monitors > Priority One InactivityCheck this Priority One Inactivity setting. this is the one updating the incident in the background based on scheduled time.Related LinksCheck the documentation: Set an inactivity monitor