This document describes how a content author can troubleshoot reference errors in Tidal Enterprise Orchestrator.
The information in this document is based on the Tidal Enterprise Orchestrator 2.1 or later.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
When a process is run, the process fails with one of these error messages:
Unable to fully resolve expression, as Reference to Property ResolvedTarget.Id
of ActivityInstance 65d28d16-5d67-44b5-8be7-a4fb7943215c. could not be resolved.
Unable to fully resolve expression, as Reference to Property
ResultTable.FirstRow.NameOfRow of ActivityInstance
1375aeb0-25c7-4cee-b96e-d41d31f5bfd1. could not be resolved.
In order to troubleshoot, the content author should look at the areas to which the variable reference points. Note that the first error points to a Target, and the second error points to a Table.
Complete these steps:
Check the configuration of the activity where the process failed. There could be a bad reference or a deprecated activity reference there.
If using triggers, make sure the trigger is what started the process. That is, you cannot have a process triggering on a CCMS alert, reference that alert in your process, and then start the process ad-hoc. That will not work.
If using tables or variables, make sure those variables contain something, or errors might occur.
If using target properties, make sure the target exists or is in the target group attempting to be referenced.