Flow never executes and stuck in the queued state for some usersIssue The flow never executes and stuck in the queued state for some usersReleaseAll VersionsCauseThe User ID field in the sys_user table is set to more than a length of 40 [Example: cde.junior.@servicenow.com.br]The created by field on sys_flow_context table TRUNCATES the id and then saves it as 40 characters.When the flow actually tries to execute, it doesn't find the user and hence fails to execute.This is causing empty flow names in flow-context - causing the original flow to appear to be hung/queued state and never executeResolutionPlease reduce the length of the impacted user's user_id