View execution logs

Application Integration generates detailed execution logs for every run of an integration. You can use the execution logs to troubleshoot failed integration runs, identify the execution status of each step in an integration, and monitor the execution status of both main and sub-integrations. For more information about logging in Application Integration, seeIntroduction to logs.

Note: Application Integration retains the execution logs of an integration for a maximum period of 32 days.

View integration execution logs

You can view the execution logs in the Google Cloud console or using the API.

Note: If the execution logs size is greater than 300 MB, Application Integration throws theResponse size too large error and logs don't load on theExecution Logs page. In that case, use theprojects.locations.integrations.executions.list method as explained in theAPI tab.

Console

To view the execution logs in the Google Cloud console, perform the following steps:

  1. In the Google Cloud console, go to the Application Integration page.

    Go to Application Integration

  2. In the navigation menu, clickLogs.

    TheExecution Logs page appears listing the execution logs generated for the integrations in the default region. The following attributes are displayed for each execution log message:

  3. To view region specific execution logs, change the region from theRegion list.
  4. Optionally, you can click refresh Refresh Logs to reload the current log list.

    The following image shows a sample Application IntegrationExecution Logs page.

    image showing the Application Integration Execution Logs pageimage showing the Application Integration Execution Logs page

API

If the size of the execution logs is greater than 300 MB, Application Integration throws theResponse too large error error and logs don't load on theExecution Logs page. In this case, you must use theprojects.locations.integrations.executions.list method to get the logs. To view logs using the API method, follow these steps:

  1. To get the execution ID for which you want to view the execution logs, construct aGET request using theprojects.locations.integrations.executions.list method with thesnapshotMetadataWithoutParams parameter set toTRUE:
    curl -v -X GET \    -G \    -H "Content-Type: application/json" \    -H "Authorization: Bearer $(gcloud auth print-access-token)" \    'https://integrations.googleapis.com/v1/projects/PROJECT_ID/locations/LOCATION/integrations/INTEGRATION_NAME/executions' \    -d "snapshotMetadataWithoutParams=true"

    Replace the following:

    • PROJECT_ID: the ID of your Google Cloud project.
    • LOCATION: the region of the integration.
    • INTEGRATION_NAME: the name of the integration.

    Execution IDs are returned in the response. Copy the execution ID for which you want to view logs.

  2. To get the execution log for the execution ID, construct aGET request using theprojects.locations.integrations.executions.list method with a filter on the execution ID that you copied in the previous step:
    curl -X GET \    -G \    -H "Content-Type: application/json" \    -H "Authorization: Bearer $(gcloud auth print-access-token)" \    'https://integrations.googleapis.com/v1/projects/PROJECT_ID/locations/LOCATION/integrations/-/executions' \    -d 'filter=executionId=EXECUTION_ID'

    Replace the following:

    • PROJECT_ID: the ID of your Google Cloud project.
    • LOCATION: the region of the integration.
    • EXECUTION_ID: the execution ID copied from the previous step.

    In the response, see theExecutionDetails field to view the log details.

    Alternatively, in the Google Cloud console, you can filter execution logs by the execution ID.

    3. Example: Filter logs

    If you want to filter the response to list logs for all integrations expect for one integration, use the following format:

    curl -X GET \    -G \    -H "Content-Type: application/json" \    -H "Authorization: Bearer $(gcloud auth print-access-token)" \    'https://integrations.googleapis.com/v1/projects/PROJECT_ID/locations/LOCATION/integrations/-/executions' \    -d 'filter=workflowName!=INTEGRATION_NAME'

    Replace the following:

    • PROJECT_ID: the ID of your Google Cloud project.
    • LOCATION: the region of the integration.
    • INTEGRATION_NAME: the name of the integration.

View task execution details

You can view detailed logs about the execution of each task in an integration or sub-integration. To view the task execution details, go to theExecution Logs page and expand the name of the integration for which you want to view the task execution details.

TheExecution Logs page displays a list of execution logs for the integration. Each execution log corresponds to a specific run of the integration.

Filter logs

You can filter the logs based on criteria such as, integration name, execution ID, date or time range, execution status, variable type, and variable name or value. To add a filter for the test case executions, use the following format:

Integration name:INTEGRATION_NAME:TEST_CASE_NAME.

Replace the following:

  • INTEGRATION_NAME: the integration name that contains functional tests.
  • TEST_CASE_NAME: the name of the test case for which you want to list the test executions.

Example:Integration name:example-integration-name:example-test-case.

Use logs to troubleshoot

The following section explains how to troubleshoot failures for the following uses cases:

Troubleshoot integration failures

Execution log messages can be valuable resources when troubleshooting unsuccessful integration runs.

For example, if an integration failed to run in a specific timeframe, use these steps to access and filter the logs to troubleshoot the failure:

  1. Search for or select the integration to troubleshoot from theIntegrations list and click to open the integration editor.
  2. ClickLogs in the toolbar of the integration editor to view the log messages.
  3. In theExecution log filter field, selectIntegration name and enter the name of the integration for which you want to view the logs.
  4. ClickEnter.
  5. To display failed integrations, in theExecution log filter field, selectExecution status to display the status list and then selectFailed.
  6. To display failed integrations between a specific time range, in theExecution log filter field, selectStart date after and enter the desired time in the valid format. Then, selectEnd date before and enter the desired time. Multiple filters are combined using the AND condition by default.

If the integration failed during the filtered time frame, theExecution Logs page displays a list of log messages. Each log message corresponds to a specific failed run of the integration.

For information about troubleshooting failed execution logs using AI, seeTroubleshoot failed execution logs using AI.

View stack trace exceptions

To view the list of exceptions, click any log message. Click the links in each exception message to view the complete stack trace of the exception.Note: Execution log message event parameters (string or JSON) are truncated with a limit of 2000 characters.

image showing logs exception errors expandedimage showing logs exception errors expanded

Trace connector failures

You can use the execution log messages to troubleshoot and trace failedconnectors task executions. Log data of a failed connector task is stored usingCloud Logging and can be viewed in the Logs Explorer.Note: Log data of a failed connectors task is available in Logs Explorer only if Cloud Logging is enabled for the respective connection in Integration Connectors. SeeView connector logs for more details.

Perform the following steps to access the log data of a failed connector task from Application Integration:

  1. Go to theExecution Logs page of your desired integration.
  2. Expand the log message of your failed execution, and stack trace to the row containing the failedConnectors task.
  3. In theStatus column, clickFailed.

    image showing logs of a failed connector taskimage showing logs of a failed connector task

    4. Application Integration automatically runs the required query for the failed connectors task and opens the Logs Explorer page to display the detailed execution log data.

To manually retrieve the log data of a failed connectors task, you can run the following query in the Logs Explorer'sQuery page. For more information about how to use Logs Explorer, seeLogs Explorer interface.

Query format

resource.type="connectors.googleapis.com/Connection"jsonPayload.integration_connectors_trace_id="EXECUTION_ID_EXECUTION_TASK_ID_EXECUTION_ATTEMPT_NUMBER"

Example

resource.type="connectors.googleapis.com/Connection"jsonPayload.integration_connectors_trace_id="9db51e4b-7d57-473d-931f-cc27b282dfad_1_2"

Download logs

You can download logs for a specific integration execution to help with debugging and analysis. The logs contain detailed information about the execution process, including timestamps, events, and any errors encountered.

To download the execution logs of an integration, perform the following steps:

  1. Go to theExecution Logs page.
  2. In the row corresponding to the integration execution for which you want to download the logs, click (Actions menu) and then selectDownload.

    3. The execution logs are downloaded as a JSON file to your browser's default download folder.

Limitation

  • Iflocal logging is disabled for an integration, then the execution logs are not generated for that integration.

What's next

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-02-19 UTC.