Scenario
A workflow runs correctly for some records, but completely skips others that appear to meet the same criteria.
Common symptoms include:
- Some transactions trigger the workflow while others do not.
- Workflow history is missing for certain records.
- Actions, emails, or field updates occur inconsistently.
- The workflow works during testing but skips records in Production.
This is a common SuiteFlow issue caused by initiation conditions, record state differences, execution contexts, or conflicting customizations.
Solution
Review the workflow configuration and skipped records carefully to identify what differs between working and non-working records.
Common causes include:
- Workflow Initiation Conditions
- Review the workflow initiation conditions carefully.
- Even small differences in:
- Status
- Subsidiary
- Department
- Form
- Field values
- can prevent records from qualifying.
- Incorrect Trigger Type
- Verify the workflow supports the correct event:
- Create
- Edit
- View or Update
- Records edited through imports or integrations may not trigger workflows configured only for manual edits.
- Execution Context Restrictions
- Workflows may skip records created through:
- CSV imports
- Web services
- Scheduled scripts
- Integrations
- Inline editing
- Review execution context settings carefully.
- Workflow Conditions Within States
- The workflow may initiate successfully but fail to enter certain states due to state conditions.
- Different Forms or Roles
- Certain forms, roles, or subsidiaries may affect field availability or workflow logic.
- Locked or Approved Records
- Approved, closed, or locked records may prevent workflow processing or updates.
- Field Value Timing
- Some fields may not contain values yet when the workflow evaluates conditions.
- Sourced or formula fields are especially sensitive to timing issues.
- Conflicting Workflows or Scripts
- Other workflows or SuiteScripts may alter field values before your workflow evaluates the record.
Notes
Records that appear identical visually may still contain important differences affecting workflow qualification, including:
- Internal status values
- Form usage
- Execution context
- Role permissions
- Workflow timing
When troubleshooting:
- Compare a working record against a skipped record directly.
- Review Workflow History logs.
- Test using the Administrator role.
- Simplify initiation and transition conditions temporarily.
- Test on standard forms where possible.
Testing workflow changes in a sandbox environment is strongly recommended before updating production workflows.