General Workflow Issues

The workflow did not process for you during testing.

Take one of the following actions:

1. Make sure that the Owner field on the workflow definition page is your user account. If the workflow release status is set to Testing, the workflow only runs for the owner of the workflow.

2. If there is a workflow initiation condition, make sure that the record meets the condition and that the condition can evaluate to true. A workflow does not initiate if the workflow initiation condition does not evaluate to true.

3. If the workflow runs on a schedule, make sure that the workflow release status is Released. If the release status is Testing, the workflow will not run on a schedule.

Users report that when the record in the workflow loads into the browser, the browser hangs and they cannot enter data.

If you set a formula in the Condition Builder, check the syntax of the JavaScript or SQL formula.

If you set a workflow action to run on a client trigger, the formula in the Condition Builder must be a JavaScript formula. If you set the action to occur on a server trigger, the formula in the Condition Builder must be a SQL formula.

You receive the following error message:

Notice (SuiteScript) : Workflow Execution Usage Limit Exceeded

Take one of the following actions:

1. Check the actions in each workflow state. Make sure that the number of actions in each state do not exceed the 1000 unit usage limit. For more information about workflow governance limits, see Script Type Usage Unit Limits.

2. Check for an infinite loop. For example, if you have a workflow that transitions from State 1 to State 2, and then from State 2 back to State 2 more than 50 consecutive times, the system identifies it as an infinite loop and a throws the “Workflow Execution Usage Limit Exceeded” error.

In an approval routing workflow, the Next Approver field is not set correctly.

For more information, see FAQ: SuiteFlow.

The workflow did not complete its execution.

Take one of the following actions:

1. Determine if the workflow executed. For example, if the workflow runs on an Opportunity record, go to a new Opportunity record to see if the workflow executed on that record. Check the Workflow History subtab on the opportunity record to see which states the record entered in the workflow.

2. Check the transitions. For example, an Opportunity record enters a workflow with two states, State 1 and State 2. If the record did not enter State 2, view the workflow definition and check the transition from State 1 to State 2. Look for errors in the transition definition or any errors in the condition.

Field value in actions or conditions always returns a null value.

If you create a workflow that includes a field value in actions or conditions and it always returns a null value, you could be experiencing an issue with permissions. To resolve this issue, check the Execute As Admin box in the workflow definition. For more information, see Execute As Admin.

If you create a workflow that is triggered by the inline edit action, the field value in actions or conditions may return a null value. The reason for this is that the record that the workflow runs on may not be loading completely because of the inline edit action.

In a workflow with an Add Button action, the role of the user who interacted with the button is incorrectly listed as Administrator in the System Notes.

If you create a workflow that includes an Add Button action, when a user interacts with the button and the record is saved, the System Notes will list the role of the user as Administrator, regardless of the role the user is logged in as. This behavior is expected and is not related to the Execute As Admin property.

The scheduled workflow did not run as expected.

If you schedule workflows to run on saved searches on SuiteApp bundles, you must have the SuiteApp Marketplace permission assigned or the scheduled workflow will not run as expected.