TheReturntask lets you customize the error messages corresponding to the HTTP response codes that are returned during an integration execution failure.
You can modify or customize error messages for the following HTTP response codes:
HTTP code
Canonical code
400
INVALID_ARGUMENT
400
OUT_OF_RANGE
401
UNAUTHENTICATED
403
PERMISSION_DENIED
404
NOT_FOUND
409
ALREADY_EXISTS
429
RESOURCE_EXHAUSTED
499
CANCELLED
Configure the Return task
To configure theReturntask:
In the Google Cloud console, go to theApplication Integrationpage.
TheIntegrationspage appears listing all the integrations available in the Google Cloud project.
Select an existing integration or clickCreate integrationto create a new one.
If you are creating a new integration:
Enter a name and description in theCreate Integrationpane.
Select a region for the integration.
Select a service account for the integration. You can change or update the service account details of an integration any time from theinfoIntegration summarypane in the integration toolbar.
ClickCreate. The newly created integration opens in theintegration editor.
In theintegration editornavigation bar, clickTasksto view the list of available tasks and connectors.
Click and place theReturntask element in the integration editor.
Click theReturntask element on the designer to open theReturntask
configuration pane.
Configure the displayed fields using theConfiguration propertiesfor the task
as detailed in the tables below.
All changes to the properties are saved automatically.
Configuration properties
The following table describes the configuration properties of theReturntask.
Property
Data type
Description
HTTP code
Integer
The4XXHTTP code for which you want to customize the error message.
Customized return message
String
The custom error message for the specified HTTP code.
Error handling strategy
An error handling strategy for a task specifies the action to take if the task fails due to atemporary error. For information about how to use an error handling strategy, and to know about the different types of error handling strategies, seeError handling strategies.
[[["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-09-04 UTC."],[[["\u003cp\u003eThe \u003cstrong\u003eReturn\u003c/strong\u003e task allows users to customize error messages for specific HTTP response codes that occur during integration execution failures.\u003c/p\u003e\n"],["\u003cp\u003eUsers can modify error messages for a range of HTTP codes, including 400, 401, 403, 404, 409, 429, and 499, each associated with a specific canonical error code.\u003c/p\u003e\n"],["\u003cp\u003eConfiguring the \u003cstrong\u003eReturn\u003c/strong\u003e task involves navigating to the Application Integration page, selecting an integration, placing the \u003cstrong\u003eReturn\u003c/strong\u003e task in the editor, and setting the desired HTTP code and custom error message.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003cstrong\u003eReturn\u003c/strong\u003e task configuration properties include specifying the HTTP code and the customized return message to be displayed upon error.\u003c/p\u003e\n"],["\u003cp\u003eUsers can find information on error handling strategies and quotas and limits for the return task in the documentation.\u003c/p\u003e\n"]]],[],null,["# Return task\n\nSee the [supported connectors](/integration-connectors/docs/connector-reference-overview) for Application Integration.\n\nReturn task\n===========\n\nThe **Return** task lets you customize the error messages corresponding to the HTTP response codes that are returned during an integration execution failure.\nYou can modify or customize error messages for the following HTTP response codes:\n\nConfigure the Return task\n-------------------------\n\nTo configure the **Return** task:\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 **Return** task element in the integration editor.\n6. Click the **Return** task element on the designer to open the **Return** task configuration pane.\n7. Configure the displayed 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 **Return** task.\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)."]]
