| ms.service | azure-logic-apps |
|---|---|
| ms.author | estfan |
| author | ecfan |
| ms.date | 02/18/2026 |
| ms.topic | include |
This section describes guidance to help troubleshoot errors or problems that you might encounter when you build or run agentic workflows.
The workflow run history provides useful information that helps you learn what happened during a specific run. For an agentic workflow, you can find tool execution inputs and outputs for a specific agent loop iteration.
-
On the workflow menu, under Tools, select Run history to open the Run history page.
-
On the Run history tab, in the Identifier column, select the workflow run that you want.
The monitoring view opens to show the status for each step.
-
Select the agent action that you want to inspect. To the right side, the Agent log pane appears.
This pane shows the agent log, including tool executions during the interaction.
-
To get tool execution data at a specific point, find that point in the agent log, and select the tool execution reference, for example:
:::image type="content" source="media/troubleshoot-agent-workflows/tool-reference-links.png" alt-text="Screenshot shows agent log and selected tool execution link." lightbox="media/troubleshoot-agent-workflows/tool-reference-links.png":::
This action moves you to the matching tool in monitoring view. The agent action shows the current iteration count.
-
In monitoring view, select the agent action or the action with the inputs, outputs, and properties that you want to review.
The following example shows a selected action for the previously selected tool execution:
:::image type="content" source="media/troubleshoot-agent-workflows/tool-execution-data.png" alt-text="Screenshot shows monitoring view, current agent loop iteration, and selected action with inputs and outputs at this point in time." lightbox="media/troubleshoot-agent-workflows/tool-execution-data.png":::
If you select the agent, you can review the following information that passes into the model and returns from the model, for example:
- Input messages passed into the model.
- Output messages returned from the model.
- Tools that the model asked the agent loop to call.
- Tool results that passed back into the model.
- Number of tokens that each request used.
-
To review a different agent loop iteration, in the agent, select the left or right arrow.
If you set up Application Insights or advanced telemetry for your workflow, you can review the logs for agent loop events, like any other action. For more information, see Enable and view enhanced telemetry in Application Insights for Standard workflows in Azure Logic Apps.
If your agent's log history exceeds the model's context length, or the maximum number of input tokens, you get an error that looks like the following example:
This model's maximum context length is 4097 tokens. However, you requested 4927 tokens (3927 in the messages, 1000 in the completion). Please reduce the length of the messages or completion.
Try reducing the limit on the number of tokens or messages that your agent loop keeps in the log and passes into the model for the next interaction. For this example, you might select Token count reduction and set Maximum Token Count to a number below the error's stated maximum context length, which is 4097.
For more information, see Manage chat history context length.