Workflow didn't create a project
Updated
Applies to: Super Admins, Creators and Integrators who have access to workflows
When a workflow doesn't create a project, its run history shows why. This article helps you find the run for your CRM record, read what happened, and get the project created.
Workflows are available when they're turned on for your organization. If you don't see Workflows in the left-hand navigation, contact your OnRamp team. Contributors and Collaborators don't see Workflows.
Why it happens
OnRamp processes each workflow step in order. If a step fails, project creation stops and the run is logged with details. A run can also end without a project on purpose: it may be waiting for approval, it may have been declined, or it may have ended on a branch set to stop.
Fix it
In the left-hand navigation, select Workflows, then select the workflow.
At the top of the workflow's left panel, select the Runs icon. The four icons there are Runs, Activity, Versions and Settings.
Set the filters so your run shows up. Unless you've changed them, the list shows only Pending Approval runs from Today. Change Date Range (for example, to All time), change Statuses, or select Reset.
To find one CRM record, enter its ID in Search objects.... Each run in the list shows its External ID.
Check the run's status, then select the run. You'll see a visual breakdown of the workflow's steps.
Select the step where the run stopped. Its Details show the message for that step, including any error.
Fix what that step needs, using the sections that follow.
Re-run the run, or test with another record. To re-run, select Re-run in the run's detail. You see Re-run only if you can publish the workflow; if you can't, ask someone who can. It's turned off while the run is still processing. See Re-run a workflow execution and Test a workflow with Debug.
What each status means
Status | What it means |
|---|---|
Created | The run has been logged. |
Success | The run finished without an error. This doesn't always mean a project was created. |
Error | A step failed and project creation stopped. |
Pending Approval | The run is waiting for someone to approve or decline it. |
Declined | Someone declined the run, or someone re-ran it before it finished and the re-run replaced it. This run created no project. If it was re-run, look for the newer run. |
A run's Execution Details show Project. If the run made a project, it's linked there. Otherwise it reads None, or None - Pending Approval for a run that's waiting.
If there's no run for the record
Check the workflow's Settings. Processing Mode decides whether a record that was already processed can start the workflow again:
Only process external objects 1 time
Process external objects many times
Process external objects until successful
Also check that the record meets the workflow's trigger.
If the run shows Success but there's no project
The run may have ended on a branch set to stop. That's expected, not an error. The last step's message reads Workflow ended — stop execution on branch '<branch name>'. If the record should have gotten a project, check that branch's conditions.
If the run shows Pending Approval
The workflow's project step is set to Wait for approval, not Create automatically. To create the project, select the run, then select Approve. To skip it, select Decline. These buttons are turned off if you can't edit the workflow.
If the error is "Account is required"
The message starts with Account is required. No account ID found in the configuration. When OnRamp knows why, the message adds the reason after that sentence. Read that reason to choose the fix:
No account is selected in the workflow's configuration: the workflow's account step uses a fixed account, and none is selected. Open the account step, select an account under Select customer, then re-run.
The related CRM record resolved to no OnRamp account, or carries no usable account ID: the record's associated account couldn't be matched to an account in OnRamp. Check the account associated with the record in your CRM, then re-run.
Get an email when a run fails
In the workflow's Settings, choose people under Alert recipients, then select Save. Only people who can publish the workflow can change the recipients. Recipients are emailed when a run fails, at most once per clock hour each, and when a run is waiting for approval. If nobody is chosen, approval alerts go to the person who created the workflow.
Still stuck?
Contact support with these values from the run's Execution Details:
Workflow and Workflow Version
Source, Object Type and Object ID
Execution UUID and Execution Date
The message from the step where the run stopped