Flow Designer Ask for Approval Flow Action has a result of skipped even with the correct group/user in place<!-- /*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: ; } } A user had a Flow with an Ask for Approval Flow Action. The user wanted to generate approvals for a certain group in this Flow Action. Unfortunately, the system would mark this Flow Action result as skipped whenever the Flow ran. In the localhost_log file, an error message was thrown (see attachment). The log states, "Invalid Sysids(sysIDHere) in approval rule - for flow context: flowContextSysIDHere" The user was instructed on how to search the sys_user_group table for this sys_id, and upon searching, no record was returned. Then, the user searched against the Name of the group, opened that record, and compared the sys_id of that record to the one thrown in the error. In doing this, the user understood that the Flow had a broken reference to a once-present group (it was no longer present, hence the error). The user corrected this error by removing the old reference and establishing a new reference to the current group.