Orchestrator and Service Manager- runbook detects changes where there are none.

I`ve stumbled upon this weird issue, where a simple runbook which needs to detect when an incident is changed and write the incident name into a text file gets triggered out of nowhere. So basically when looking in the service manager database under table MT_system$WorkItem$Incident_Log there was no timestamp for a change action, which means…

1