Resolve flow failing to restart due to missing sysevent recordsIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } When you try to restart a flow context using the Restart UI Action on the sys_flow_context table, you may see the error: "The sysevent record for the supplied context is no longer present on the system." This error occurs when the event queue (sysevent) record associated with the flow has been deleted or purged, preventing the system from resuming the flow. This action is run on table sys_flow_context table: https://<instance>.service-now.com/sys_ui_action.do?sys_id=f7b7a87a0f69111048d04abec4767e1a Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All releases Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } After sysevent table records are created, they are automatically deleted after seven days, according to the sys_auto_flush configuration. https://<instance>.service-now.com/sys_auto_flush.do?sys_id=8d3ae216c0a8010a017850d639415ef3&sysparm_record_target=sys_auto_flush&sysparm_record_row=1&sysparm_record_rows=1&sysparm_record_list=tablenameCONTAINSevent%5Etablename%3Dsysevent The Restart UI Action verifies whether the flow was triggered by a sysevent with the name flow.fire and a parm1 value of null. If the flow context was created more than seven days prior, the corresponding sysevent record no longer exists in the system. This causes the verification check to fail, and the UI action displays the error: "The sysevent record for the supplied context is no longer present on the system." As the sysevent table records that are associated with the specific flow context have already been deleted due to the system's automatic cleanup process, it is no longer possible to restart or resume the flow context. This behavior is intentional and is part of the system's design to ensure that outdated or stale event records do not persist indefinitely. Since these sysevent records are only retained for a limited period (seven days), once they are purged, any attempt to restart the flow context will fail because the necessary event data required to trigger or continue the flow no longer exists in the system.