# Troubleshooting your Actions

In the event that your Actions project fails or seems to be working poorly, the cause of
the issue may not be obvious. From the [Actions
console](https://console.actions.google.com), you can view detailed logs for
your project that can give you more insight into what's going on.

## View your project's logs

Your project's logs can be accessed via the Actions Console under Analytics:

1. On your project in the [Actions
   console](https://console.actions.google.com), select **Analytics** in the top menu.
2. Select the **Health** tab near the top of the page.
3. Under **Errors** , select the **View Logs** link on the upper-right corner:

![](https://developers.google.com/static/assistant/console/images/troubleshoot/troubleshoot-001.png)

This link will take you to your project's logs in the Google Cloud Platform,
where you can filter, expand, and analyze the log data that has been collected.

> [!NOTE]
> **Note:** The logs for your Actions on Google project are generated using Stackdriver Logging, which offers log management and analytics. You can learn more about how to navigate your project's logs at [Viewing
> Logs](https://cloud.google.com/logging/docs/view/overview) on the Stackdriver documentation. Note that not every filter described in those docs are currently available for Actions on Google projects.

If you're using the [Actions Simulator](https://developers.google.com/assistant/console/simulator) to test your
Actions, you can quickly access logs specific to your tests by clicking the **View
Logs** link on the upper-right corner of the Actions Simulator page.

![](https://developers.google.com/static/assistant/console/images/troubleshoot/troubleshoot-002.png)

## Troubleshooting

Log entries are marked with levels that indicate urgency. If you're
troubleshooting a problem with your Actions project, you will probably
want to start by filtering for *Critical* , *Error* , and *Warning* events:

![](https://developers.google.com/static/assistant/console/images/troubleshoot/troubleshoot-003.png)

Every log entry has a summary that includes a timestamp and short description
of the event. You can correlate your project's behavior with these log timestamps
to determine if they are related, and reference the description to narrow down
the cause.

In the example below, an `UnparseableJsonResponse` error was returned, likely
as the result of a syntax or timeout error when recieving this JSON response
from the webhook:

![](https://developers.google.com/static/assistant/console/images/troubleshoot/troubleshoot-004.png)

You may also want to look for *Debug* events with a similar timestamp, as they
can include additional information about other events. By expanding an error log
and filtering by the `trace` field, the resulting list will show you all
events associated with the initial error:

![](https://developers.google.com/static/assistant/console/images/troubleshoot/troubleshoot-005.png)

> [!NOTE]
> **Note:** If the resulting trace filter doesn't show any additional results beyond the initial log, see if there is a *severity* line in the filter and try removing it.

In the example below, the debug messages associated with the original
error give us additional information about the issue, including a detailed
error description and the specific JSON response that caused the issue:

![](https://developers.google.com/static/assistant/console/images/troubleshoot/troubleshoot-006.png)

## Disabling log types

Since the logs for your project are comprehensive, you may find it valuable to
exclude certain event types from appearing in your logs by default (such as
events with PII or events that you deem to be clutter). You can create
exclusions on your project's log page by navigating to **Resource usage** on the
left navigation bar and selecting the **Exclusions** tab:

![](https://developers.google.com/static/assistant/console/images/troubleshoot/troubleshoot-007.png)

You can learn more about excluding different log events at [Excluding
Logs](https://cloud.google.com/logging/docs/exclusions) on the Stackdriver
documentation.