Flow trigger not firing: record-based trigger condition not met

The trigger condition script or field condition is evaluating to false for the record operation, preventing the flow from executing. (high likelihood)

The flow is set to trigger on the wrong table or the record operation is happening on a different table than specified in the trigger configuration. (high likelihood)

The flow is inactive, deactivated, or in draft state, preventing it from responding to trigger events even when conditions are met. (medium likelihood)

The trigger timing is set incorrectly (before/after) for the type of condition being evaluated, causing the condition to fail due to field state timing. (medium likelihood)

User permissions or ACL restrictions are preventing the flow from accessing the triggering record or evaluating the condition properly. (low likelihood)

Step 1: Navigate to Flow Designer and locate the problematic flow, then verify the flow status is 'Active' in the flow properties.

Step 2: Open the trigger configuration and confirm the 'Table' field matches the table where record operations are occurring.

Step 3: Review the trigger condition by clicking 'Edit condition' and test the condition logic against sample records that should trigger the flow.

Step 4: Check the trigger timing setting (Run trigger when) and ensure it's appropriate for your condition - use 'after' for evaluating final field values.

Step 5: Test the flow by creating or updating a record that should meet the trigger conditions, then check Flow Designer execution details for results.

Step 6: If the condition still fails, add logging to the condition script using gs.info() to output field values and condition evaluation results.

Step 7: Verify the user context under which the flow runs has read access to all fields referenced in the trigger condition.

Step 8: Check System Log at System Diagnostics > Logs > System Log for any additional error details or access control violations.