sys_trigger jobs are in -1776 state and the scheduled jobs are not runningIssue Several jobs in sys_trigger have state -1776 and the scheduled jobs are not running for a specific duration of time as shown in screenshot below ReleaseWashington and higher releaseResolution Sys_trigger records are explicitly set to -1776 if ATF test suite (sys_atf_schedule) is configured in the instance. Part of running an ATF performance test is suspending all processing of sys_triggers in order to guarantee a consistent result. This is implemented in out of the box source code by setting sys_trigger records to -1776 by a scheduled job with name "ATF Test Dispatcher". When "ATF Test Dispatcher" executes, it sets sys_trigger records to -1776.The sys_trigger records return to their original state after completion of the ATF performance profiling suite Both step 1 and step 2 mentioned above are expected behavior when ATF test suite (sys_atf_schedule) is configured. The State value of -1776 is used in order to differentiate them as "triggers suspended by ATF" vs e.g. "trigger that the user disabled intentionally". There will be impact on sys_trigger job execution depending on the frequency of sys_atf_schedule script. Example if the ATF test script is scheduled to run daily at a specific time then all the sys_trigger records will be in state -1776 on a daily basis for a specific duration of time. Refer to ATF Test Suite script behavior for more details If ServiceNow instance is setup to execute ATF test scripts please inform your team about this and the expected behavior of scheduled jobs during the window.