This document describes how integration execution logs are saved in Application Integration and how to enable local logging for your integrations.
Overview
Local logging refers to the integration's data or metadata that is saved during its execution. Application Integration
uses the saved data to generate the integration execution logs.
You can set the Local logging to any of the following three modes:
Enable(sync): The log data is persisted (written) during integration's execution. In this mode, Application Integration writes the log data synchronously
after each execution step. This mode guarantees the generation of logs for all the integration executions.
Use this mode if your priority is to have a guaranteed generation of logs, and a latency in
integration execution time is acceptable.
Enable(async): By default, local logging for an integration is enabled in async mode.
The log data is persisted (written) at fixed intervals or after the completion of the integration's execution, whichever is earlier. In this mode, the
integration takes a relatively lesser time to execute when compared to Enable(sync) mode,
because Application Integration writes the log data asynchronously
during the integration execution. However, this mode doesn't guarantee the generation of logs for all the executions. In rare cases, it's possible that logs aren't generated for an integration execution.
Use this mode if your priority is to run your integrations with reduced latency, and the guaranteed
generation of logs is relatively of a lesser importance.
Disable: The execution logs aren't generated for the integration. Disabling the local logging improves the overall integration latency, as log events aren't generated for request and response parameters, and other integration variables.
Configure local logging
To configure the local logging for your integration, do the following steps:
In the toolbar, click settingsIntegration settings.
From the Local logging list, select the local logging mode. By default, Local logging is set to Enable(async).
Click Done.
Retention period
The retention period for integration execution logs is 90 days. If you want to modify the retention period, you must enable Cloud Logging and configure the retention period for your project. For more information, see Logging retention.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-26 UTC."],[[["\u003cp\u003eThis document outlines how Application Integration saves integration execution logs and how to enable local logging for integrations.\u003c/p\u003e\n"],["\u003cp\u003eLocal logging can be set to three modes: \u003ccode\u003eEnable(sync)\u003c/code\u003e for guaranteed log generation, \u003ccode\u003eEnable(async)\u003c/code\u003e for reduced latency, or \u003ccode\u003eDisable\u003c/code\u003e for the best integration latency, but no logs.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eEnable(sync)\u003c/code\u003e mode writes log data synchronously after each step, ensuring log generation, while \u003ccode\u003eEnable(async)\u003c/code\u003e writes data asynchronously, potentially missing some logs.\u003c/p\u003e\n"],["\u003cp\u003eLocal logging settings can be configured within the integration editor by accessing the settings menu and selecting the desired mode from the "Local logging" dropdown.\u003c/p\u003e\n"],["\u003cp\u003eIntegration execution logs are retained for 90 days by default; however, the retention period can be modified by enabling Cloud Logging and setting a new retention period for the project.\u003c/p\u003e\n"]]],[],null,["# Local logging\n\nSee the [supported connectors](/integration-connectors/docs/connector-reference-overview) for Application Integration.\n\nLocal logging\n=============\n\nThis document describes how integration execution logs are saved in Application Integration and how to enable local logging for your integrations.\n\nOverview\n--------\n\nLocal logging refers to the integration's data or metadata that is saved during its execution. Application Integration\nuses the saved data to generate the [integration execution logs](/application-integration/docs/integration-execution-logs).\n\nYou can set the **Local logging** to any of the following three modes:\n\n- **Enable(sync):** The log data is persisted (written) during integration's execution. In this mode, Application Integration writes the log data synchronously after each execution step. This mode guarantees the generation of logs for all the integration executions.\n\n Use this mode if your priority is to have a guaranteed generation of logs, and a latency in\n integration execution time is acceptable.\n- **Enable(async):** By default, local logging for an integration is enabled in async mode. The log data is persisted (written) at fixed intervals or after the completion of the integration's execution, whichever is earlier. In this mode, the integration takes a relatively lesser time to execute when compared to `Enable(sync)` mode, because Application Integration writes the log data asynchronously during the integration execution. However, this mode doesn't guarantee the generation of logs for all the executions. In rare cases, it's possible that logs aren't generated for an integration execution.\n\n Use this mode if your priority is to run your integrations with reduced latency, and the guaranteed\n generation of logs is relatively of a lesser importance.\n- **Disable:** The execution logs aren't generated for the integration. Disabling the local logging improves the overall integration latency, as log events aren't generated for request and response parameters, and other integration variables.\n\nConfigure local logging\n-----------------------\n\nTo configure the local logging for your integration, do the following steps:\n\n1. Open your integration in the [integration editor](/application-integration/docs/integrations-ui-layout).\n2. In the toolbar, click **settingsIntegration settings**.\n3. From the **Local logging** list, select the [local logging mode](#overview). By default, **Local logging** is set to **Enable(async)**.\n4. Click **Done**.\n\n| **Tip:**Disabling the local logging improves the overall integration latency, as log events aren't generated for request and response parameters, and other integration variables.\n\nRetention period\n----------------\n\nThe retention period for integration execution logs is 90 days. If you want to modify the retention period, you must enable Cloud Logging and configure the retention period for your project. For more information, see [Logging retention](/logging/docs/routing/overview#logs-retention).\n\nQuotas and limits\n-----------------\n\nFor information about quotas and limits, see [Quotas and limits](/application-integration/docs/quotas).\n\nWhat's next\n-----------\n\n- Learn about [all tasks and triggers](/application-integration/docs/all-triggers-tasks).\n- Learn how to [test and publish an integration](/application-integration/docs/test-publish-integrations).\n\n- Learn about [error handling](/application-integration/docs/error-handling-strategy).\n- Learn about [integration execution logs](/application-integration/docs/introduction-logs)."]]
