Workflow agent logs

After your workflow agent runs, you can view a log of that execution in Optimizely Opal to debug the agent and see how it is performing.

Access your agents

1. Go to home.optimizely.com
2. Select your organization.

3. Select Opal.

   

4. Click Agents. 

   

5. Select the Your Agents tab.

   

View the logs

Workflow agent logs are accessible from two locations, the Agents page and the workflow editor.

From the Agents page

To access the logs of a workflow agent from the Agents page, complete the following:

1. Complete the steps in the Access your agents section.

2. Select the Workflow Logs tab.

   

3. Click a workflow's execution to view its logs.

From the workflow editor

1. Complete the steps in the Access your agents section.
2. Click the agent name, or click More (...) > Edit Agent.
3. Click More (...) > View Logs.
4. Click an execution to view its logs.

Workflow agent log overview

Started

The workflow agent's log that is still running displays similar to the following:

1. Details – Toggle the details panel of the execution on or off.
2. Name – The name of the workflow agent.
3. Timestamp – The timestamp of when the workflow agent started.
4. Status – Indicates the workflow agent is still running.
5. Cancel Execution – Stop the workflow agent.
6. Close details – Close the details panel of the execution.
7. Agent Name – The name of the workflow agent.
8. Execution ID – The unique ID of the workflow agent's execution. Use this ID to identify a specific agent run.
9. Execution Time  – The timestamp of when the workflow agent executed started.
10. Triggered By – The name of the person who ran the workflow agent. If the workflow agent is started from a webhook, the user who created the workflow agent displays instead.
11. Input Variables – The variables that were used in this execution. Click Copy to copy the variables to your clipboard to easily reference and debug agent runs.
12. Output – Opal's response including any error messages.
13. Execution Memory – The memory chunks the agent transversed during the agent workflow's execution. 
14. Agents run in this workflow – The overview of the agents invoked in this execution. They display as gray because they have not run yet.
15. Close – Return to the list of the workflow agent's executions. 
16. Overview map – A smaller, "picture-in-picture" view of the entire workflow agent.

Completed and failed

The workflow agent's log with a Completed or Failed status displays similar to the following:

1. Details – Toggle the details panel of the execution on or off.
2. Name – The name of the workflow agent.
3. Status – If the workflow agent successfully completed or failed.
4. Timestamp – The timestamp of when the workflow agent started.
5. Agent Name – The name of the workflow agent.
6. Execution ID – The unique ID of the workflow agent's execution. Use this ID to identify a specific agent run.
7. Execution Time  – The timestamp of when the workflow agent started.
8. Triggered By – The name of the person who ran the workflow agent. If the workflow agent is started from a webhook, the user who created the workflow agent displays instead.
9. Duration – Total time of how long the workflow agent took to execute.
10. Credits – Approximate credit usage for this workflow. This total accounts for both the workflow orchestrator and specialized agents used. Final usage may vary slightly. See Optimizely Opal credits.
11. Input Variables – The variables that were used in this execution. Click Copy to copy the variables to your clipboard to easily reference and debug agent runs.
12. Output – Opal's response including any error messages.
13. Execution Memory – The memory chunks the agent traversed during the agent workflow's execution. 
14. Agents run in this workflow – The overview of the agents invoked in this execution. You can click agents to see their run details. See Specialized agent logs overview for information.
15. Close – Return to the list of the workflow agent's executions. 
16. Overview map – A smaller, "picture-in-picture" view of the entire workflow agent.

Additional elements

If your workflow agent includes logic elements, such as a Condition or Loop, Opal tracks the following execution statuses in the logs:

• Pending – Not yet started.
• Running – Currently executing.
• Completed – Finished successfully.
• Failed – Encountered an error.
• Skipped – Intentionally skipped.
• Cancelled – Cancelled by user.

If agents in the workflow include tool calls, the parameter generation logs display within the Thinking chunks of the workflow execution log. The logs capture how Opal interprets input, isolates the required parameters, and formulates the JSON structure passed from one agent to the next. Use this information to verify that parameters were predicted as expected or to diagnose issues when a workflow produces unexpected results.

For example in the following image, Opal distills a user's starting input into a structured parameters object, such as a news_topics field populated with relevant values.