"The sysevent record for the supplied context is no longer present on the system" while restating the flow using 'Restart UI' Action on flow ContextIssue <!-- /*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: block; max-width: ; width: auto; height: auto; } } When we try to restart the flow context using Restart UI Action but got the error below: "The sysevent record for the supplied context is no longer present on the system." -This means that the event queue (sysevent) record associated with that flow has been deleted or purged, and as a result, the system cannot resume or nudge the flow anymore. https://<instance>.service-now.com/sys_ui_action.do?sys_id=f7b7a87a0f69111048d04abec4767e1aThis is run on table sys_flow_context table. 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: block; max-width: ; width: auto; height: auto; } } 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: block; max-width: ; width: auto; height: auto; } } As per sys_auto_flush records:Record in sysevent table will be deleted after 7 days of it's creation: 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 This UI action needs to verify whether the flow was triggered by a sysevent with the name flow.fire and a parm1 value of null. However, since sysevent records are only retained for 7 days, if the associated flow context was created more than 7 days ago, the corresponding sysevent no longer exists. As a result, the check fails and the UI action does not function as expected and throws error - 'The sysevent record for the supplied context is no longer present on the system'.