통합 실행이 정지되어야 하는 시간(분)입니다. 최대 시간 제한은 44640분(31일)이며 기본값이기도 합니다.
통합 실행이 지정된 제한 시간 내에 재개되지 않으면 제한 시간이 만료된 후 통합에서 자동으로 실행을 재개하고 Suspension result 변수 값을 Expired로 설정합니다.
Suspension result
문자열
정지 태스크 결과를 저장하는 변수입니다. 값을 이 변수로 설정하는 것은 선택사항입니다. 이 변수를 요구사항에 따라 어떠한 값으로도 설정할 수 있습니다. 이 변수는 통합 실행 흐름을 보다 세밀하게 제어하려는 경우에 유용합니다. 예를 들어 정지 결과를 읽고 모든 다운스트림 태스크의 값을 기준으로 조건부 결정을 구성할 수 있습니다.
Suspension Id
문자열
정지 태스크의 고유 식별자입니다. 이 변수 값은 통합이 정지된 직후에 설정됩니다. 통합 UI의 실행 로그 페이지에서 식별자 값을 가져올 수 있습니다. API를 사용하여 통합을 트리거하면 API의 응답 객체에서 식별자 값을 가져올 수도 있습니다.
정지 ID를 사용하거나 통합의 실행 ID를 사용하여 통합 실행을 재개할 수 있습니다.
Suspensions API로 정지 취소
정지 API를 사용하면 API 호출을 통해 정지를 취소할 수 있습니다. 정지 API로 정지를 취소하려면 통합 실행 ID나 정지 태스크의 정지 ID가 있어야 합니다. 정지를 취소하려면 다음 API에 POST 요청을 발행해야 합니다.
이 API에서 INTEGRATION_ID 제공은 선택사항입니다. 하지만 EXECUTION_ID 또는 SUSPENSION_ID를 제공해야 합니다. ID 값이 없으면 값을 -로 대체할 수 있습니다. 이 API에서 REGION, PROJECT, LOCATION은 필수 필드입니다.
정지를 취소하면 통합 실행이 재개되고 정지 태스크 이후의 다운스트림 태스크가 실행됩니다.
다음 예시에서는 suspensions API를 사용하여 정지를 취소하는 방법을 보여줍니다.
[[["이해하기 쉬움","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-08-07(UTC)"],[[["\u003cp\u003eThe Suspend task halts integration execution, allowing it to be resumed either after a set time or via a \u003ccode\u003eSuspensions\u003c/code\u003e API request.\u003c/p\u003e\n"],["\u003cp\u003eUnlike the Approval task, the Suspend task supports automatic resumption and doesn't require manual intervention, and unlike the Timer task, the Suspend task can be resumed via API calls.\u003c/p\u003e\n"],["\u003cp\u003eYou can configure a \u003ccode\u003eSuspension result\u003c/code\u003e variable in the Suspend task to store a custom value, which can then be used for conditional branching in downstream tasks.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eSuspensions\u003c/code\u003e API allows revoking a suspension by using either the integration's execution ID or the Suspend task's suspension ID, or both, providing flexibility in managing integration flow.\u003c/p\u003e\n"],["\u003cp\u003eThe suspension time can be configured up to a maximum of 44640 minutes (31 days), and if not resumed earlier, the integration automatically continues after this time, with the \u003ccode\u003eSuspension result\u003c/code\u003e set to \u003ccode\u003eExpired\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,["# Suspend task\n\nSee the [supported connectors](/integration-connectors/docs/connector-reference-overview) for Application Integration.\n\nSuspend task\n============\n\nThe **Suspend** task lets you temporarily pause and then resume\nthe execution of an integration.\n\nDuring an integration execution, when the control reaches a Suspend task, execution is halted, and all tasks after the Suspend task are suspended. Integration\nresumes the execution when any of the following events occur:\n\n- Expiry of the specified suspension time.\n- After receiving a resume execution request from the `Suspensions` API.\n\nYou can also configure an output variable (**Suspension result**) for the Suspend task\nand set it to any value and use the value to create branching conditions for executing the downstream tasks.\n| **Note:** When a new version of the integration is published, any suspended executions of the previous version are automatically cancelled.\n\nCompare Approval task, Suspend task, and Timer task\n---------------------------------------------------\n\nAll the three ([Approval](/application-integration/docs/approval-task),\n[Suspend](/application-integration/docs/run-suspend-task),\nand [Timer](/application-integration/docs/run-timer-task)) tasks perform a similar\nfunction of pausing and resuming an integration. However, there are subtle differences\namong them. The following table describes the differences amongst the three tasks.\n\nConfigure the Suspend task\n--------------------------\n\nTo configure the **Suspend** task, perform the following steps:\n\n1. In the Google Cloud console, go to the **Application Integration** page.\n\n [Go to Application Integration](https://console.cloud.google.com/integrations)\n2. In the navigation menu, click **Integrations** .\n\n\n The **Integrations** page appears listing all the integrations available in the Google Cloud project.\n3. Select an existing integration or click **Create integration** to create a new one.\n\n\n If you are creating a new integration:\n 1. Enter a name and description in the **Create Integration** pane.\n 2. Select a region for the integration. **Note:** The **Regions** dropdown only lists the regions provisioned in your Google Cloud project. To provision a new region, click **Enable Region** . See [Enable new region](/application-integration/docs/enable-new-region) for more information.\n 3. Select a service account for the integration. You can change or update the service account details of an integration any time from the info **Integration summary** pane in the integration toolbar. **Note:** The option to select a service account is displayed only if you have enabled integration governance for the selected region.\n 4. Click **Create** . The newly created integration opens in the *integration editor*.\n\n\n4. In the *integration editor* navigation bar, click **Tasks** to view the list of available tasks and connectors.\n5. Click and place the **Suspend** task element in the integration editor.\n6. Click the **Suspend** task element on the designer to view the **Suspend** task configuration pane.\n7. Configure the remaining fields using the [Configuration properties](#params) for the task as detailed in the tables below.\n\n\n All changes to the properties are saved automatically.\n\nConfiguration properties\n------------------------\n\n\nThe following table describes the configuration properties of the Suspend task.\n\nRevoke a suspension with the Suspensions API\n--------------------------------------------\n\nThe Suspensions API lets you revoke a suspension via a API call. To revoke a suspension with\nthe **Suspensions** API, you must have either the execution ID of the integration or\nthe suspension ID of the Suspend task. To revoke a suspension, you\nmust issue a `POST` request to the following API: \n\n```\nhttps://REGION-integrations.googleapis.com/v1/{name=projects/PROJECT/locations/LOCATION/integrations/INTEGRATION_ID/executions/EXECUTION_ID/suspensions/SUSPENSION_ID}:lift\n \n```\n\nIn this API, the \u003cvar translate=\"no\"\u003eINTEGRATION_ID\u003c/var\u003e is optional. However, you must provide\neither the \u003cvar translate=\"no\"\u003eEXECUTION_ID\u003c/var\u003e or the \u003cvar translate=\"no\"\u003eSUSPENSION_ID\u003c/var\u003e. If you don't have any of\nthe ID values, you can substitute the value with `-`. In this API, \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e, \u003cvar translate=\"no\"\u003ePROJECT\u003c/var\u003e, and \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e are required fields.\n| **Note:**\n|\n| - If you don't specify both the execution ID and the suspension ID, the API doesn't run and reports an error.\n| - If you don't specify the `suspension_result`, value of the suspension result is set to `Resolved`.\n\nAfter you revoke the suspension, integration execution resumes and executes\nthe downstream tasks after the Suspend task.\n\nThe following examples show how to revoke a suspension by using the **suspensions** API.\n\n### Example 1: Revoke a suspension with only the suspension ID\n\nThe following `curl` command shows you how to revoke a suspension when you only have the suspension ID: \n\n```\n curl -H \"Authorization: Bearer $TOKEN\" \\\n -H \"Content-type: application/json\" \\\n -H X-GFE-SSL: yes \\\n -X POST \\\n -d '{\"suspension_result\":\"Approved\"}' \\\n https://us-east1-integrations.googleapis.com/v1/projects/demo-project/locations/us-east1/integrations/-/executions/-/suspensions/c6a13a79-a918-41e2-82b9-32b5a010755a:lift\n```\n\nIn this example, the `Suspension result` variable is set to `Approved`\nfor the supension ID `c6a13a79-a918-41e2-82b9-32b5a010755a`.\n\n### Example 2: Revoke a suspension with only the execution ID\n\nThe following `curl` command shows you how to revoke a suspension when you only have the execution ID: \n\n```\n curl -H \"Authorization: Bearer $TOKEN\" \\\n -H \"Content-type: application/json\" \\\n -H X-GFE-SSL: yes \\\n -X POST \\\n -d '{\"suspension_result\":\"true\"}' \\\n https://us-east1-integrations.googleapis.com/v1/projects/demo-project/locations/us-east1/integrations/-/executions/76a391e7-c801-45d7-8046-eab20d167ec5/suspensions/-:lift\n```\n\nIn this example, the `Suspension result` variable is set to `true`\nfor the execution ID `76a391e7-c801-45d7-8046-eab20d167ec5`.\n\n### Example 3: Revoke a suspension with both the execution ID and the suspension ID\n\nThe following `curl` command shows you how to revoke a suspension when you have both the execution ID and the suspension ID: \n\n```\n curl -H \"Authorization: Bearer $TOKEN\" \\\n -H \"Content-type: application/json\" \\\n -H X-GFE-SSL: yes \\\n -X POST \\\n -d '{\"suspension_result\":\"{processname: \"Release\", owner: \"John\", status: \"approved\"};\"}' \\\n https://us-east1-integrations.googleapis.com/v1/projects/demo-project/locations/us-east1/integrations/-/executions/9b721baa-0a23-4576-b2b6-d251d163ea6f/suspensions/f01815bf-ed18-4e01-9d41-cc2ce7861e95:lift\n```\n\nIn this example, the `Suspension result` variable is set to `{processname: \"Release\", owner: \"John\", status: \"approved\"};`\nfor the suspension ID `f01815bf-ed18-4e01-9d41-cc2ce7861e95`.\n\nError handling strategy\n-----------------------\n\n\nAn error handling strategy for a task specifies the action to take if the task fails due to a [temporary error](/application-integration/docs/error-handling). For information about how to use an error handling strategy, and to know about the different types of error handling strategies, see [Error handling strategies](/application-integration/docs/error-handling-strategy).\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)."]]
