[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-06-16 UTC。"],[[["\u003cp\u003eError handling strategies in Application Integration define actions to take when a task fails due to temporary errors.\u003c/p\u003e\n"],["\u003cp\u003eYou can configure error handling for tasks by adding conditional failure policies, a default policy, and an error catcher, specifying the retry strategy and conditions.\u003c/p\u003e\n"],["\u003cp\u003eAvailable retry strategies include Fatal, Ignore, None, Restart integration with backoff, Retry task with exponential/fixed/linear backoff.\u003c/p\u003e\n"],["\u003cp\u003eRetry conditions utilize operators like =, !=, <, >, AND, OR, NOT, and functions such as \u003ccode\u003eexists()\u003c/code\u003e, \u003ccode\u003edoes_not_exist()\u003c/code\u003e, \u003ccode\u003eis_empty()\u003c/code\u003e, and \u003ccode\u003eis_not_empty()\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eFailed executions are queued and retried with an exponential backoff, gradually increasing wait times up to 10 times, capped at a default of 50 concurrent executions per project and region.\u003c/p\u003e\n"]]],[],null,["# Error handling strategies for tasks\n\nSee the [supported connectors](/integration-connectors/docs/connector-reference-overview) for Application Integration.\n\nError handling strategies for tasks\n===================================\n\nThe error handling strategy for a task specifies the action to take if the task fails\ndue to a temporary error.\n\nConfigure error handling strategies\n-----------------------------------\n\nTo configure an error handling strategy for a task, follow these steps:\n\n1. Click the existing task in your integration editor. The task configuration pane appears.\n2. In the task configuration pane, expand the **Error handling** section. The following image shows the **Error handling** section:\n\n\n In the **Error handling** section, follow these steps:\n 1. To add a new failure policy, click **+ Add Failure Policy** . If multiple conditional failure policies are configured, they are checked and matched in order.\n 1. In the **Retry strategy** field, select the error handling strategy that you want to use. For a list of strategies, see [Retry strategies](#type).\n 2. In the **Retry condition** field, enter the condition that must match the error for this error strategy to execute. For example, for a [Call REST Endpoint task](/application-integration/docs/configure-call-rest-endpoint-task), to execute the error strategy if the error code matches `404`, enter the following: \n\n ```\n $`ErrorInfo.code`$ = 404\n ```\n For information about how to add these conditions, see [Retry conditions](#retry-condition).\n 2. In the **Default error policy** section, add the default policy that must be applied if no conditional failure policy matches. The default failure policy is optional.\n 3. In the **Error catcher** section, add the [error catcher](/application-integration/docs/error-catcher) for your integration.\n\nFor information about error codes and error handling, see [Error handling](/application-integration/docs/error-handling).\n\nRetry strategies\n----------------\n\n\nThe following tables describes the different error handling strategies that you can use for a task:\n\n\n### Backoff retries\n\n\nThe default concurrency limit is set to 50 executions for each project and region. Failed executions are queued and retried using an exponential backoff algorithm, which gradually increases the wait time between retries up to 10 times. For example:\n\n1. Execute an integration.\n2. If the request fails, waits 10 minutes and retries the request.\n3. If the request fails, waits 20 minutes and retries the request.\n4. If the request fails, waits 40 minutes and retries the request.\n5. And so on, up to a maximum backoff retries of 10 times.\n\n\nRetry conditions\n----------------\n\n\nThe retry condition specifies the condition that must match for the error handling strategy to execute. The following table describes the supported operators and functions that you can use in the retry condition:\n\n### Supported operators\n\n\nThe following table describes the supported operators available for use in retry conditions.\n\n\n### Supported functions\n\n\nThe following table describes supported functions available for use in retry conditions."]]
