Scenario
A workflow is expected to run once, but instead it triggers multiple times on the same record.
Common symptoms include:
- Multiple workflow emails being sent.
- Repeated field updates.
- Duplicate notes or tasks being created.
- Workflow history showing repeated executions on a single save.
- Workflow actions triggering unexpectedly after edits.
This is a common issue in SuiteFlow environments where workflow triggers, state logic, or multiple customizations cause the workflow to reprocess the same record repeatedly.
Solution
Review the workflow configuration and record behavior to identify what is causing the repeated executions.
Common causes include:
- Workflow Trigger Configuration
- Review the workflow trigger settings carefully.
- Workflows configured for:
- Field Updates Triggering Additional Saves
- Workflow actions that update fields can trigger the workflow again if the workflow also runs on edit.
- This can create workflow loops unintentionally.
- State Re-Entry
- A workflow may continuously re-enter the same state due to transition logic or conditions remaining true after processing.
- Multiple Workflows on the Same Record
- Separate workflows may trigger each other indirectly through field updates or state changes.
- Workflow Conditions Too Broad
- Conditions that are always true can cause workflows to execute repeatedly on every save.
- Scheduled or Repeating Actions
- Scheduled workflow actions may continue running if exit conditions are not configured properly.
- Scripts Updating the Record
- SuiteScript customizations may update the record after the workflow runs, causing another workflow execution cycle.
- CSV Imports or Integrations
- External integrations or imports may repeatedly update records and retrigger workflows unexpectedly.
Notes
Repeated workflow execution is commonly caused by workflows updating fields on records that are also configured to trigger workflows on edit.
When troubleshooting:
- Review Workflow History carefully.
- Check whether the workflow runs during Create, Edit, or both.
- Identify which field updates occur immediately before repeated execution.
- Review other workflows and scripts affecting the same record type.
- Temporarily disable non-essential workflows in a sandbox for testing.
Testing workflow changes in a sandbox environment is strongly recommended before updating production workflows.