Troubleshoot Design Errors

A definition can fail during design or when you activate it. Learn how to resolve common design issues.

Fixes for Design Errors

Issue	Resolution
Activating a definition, or activating a definition created from a template definition, returns an error.	You don't have access to one or more objects specified as data sources or writeback objects. Verify these requirements: The required Setup objects are enabled (for example, from Setup in Order Settings, the Order object must be enabled) The specified objects are available in your org; and you have Read and Create permissions for the objects.
A definition can't be deactivated.	This issue occurs when one or more of the definition's runs are in progress. You can't deactivate a definition while one of its runs is in progress. From Setup, find and select Monitor Workflow Services. Confirm that the definition's runs are no longer In Process. Deactivate the definition.
A definition can't be opened because a data source object doesn't exist.	This issue occurs when someone deletes or renames the Salesforce object, dataset, or Data Lake object that's part of the data source. To restore a Salesforce object or dataset: add it back to the data source node, and try again. To restore a Data Lake object: add a Data Lake object with the same name and fields as before, and try again.

Issue

Resolution

Activating a definition, or activating a definition created from a template definition, returns an error.

You don't have access to one or more objects specified as data sources or writeback objects. Verify these requirements:

The required Setup objects are enabled (for example, from Setup in Order Settings, the Order object must be enabled)
The specified objects are available in your org; and you have Read and Create permissions for the objects.

A definition can't be deactivated.

This issue occurs when one or more of the definition's runs are in progress. You can't deactivate a definition while one of its runs is in progress.

A definition can't be opened because a data source object doesn't exist.

This issue occurs when someone deletes or renames the Salesforce object, dataset, or Data Lake object that's part of the data source.

To restore a Salesforce object or dataset: add it back to the data source node, and try again.
To restore a Data Lake object: add a Data Lake object with the same name and fields as before, and try again.

Did this article solve your issue?

Let us know so we can improve!