Custom Actions work asynchronous ?

[Michael_Soprano]

Could somebody confirm?

[SatheeskannaK]

@Michael_Soprano 

• Custom Actions within AJO are designed to operate asynchronously.
• When AJO initiates a Custom Action, it dispatches an HTTP POST/GET request to the specified external API endpoint.
• AJO's interaction with your API is limited to awaiting an immediate HTTP response, such as a "200 OK" for successful receipt, a "500 Internal Server Error" for issues on your server's side, or other standard HTTP status codes.
• Upon receiving any HTTP response, the AJO journey promptly progresses to the next step or activity. AJO does not, under any circumstances, wait for your external system to fully process the request, execute business logic, or finalize any background operations. While the underlying HTTP call itself is a synchronous communication where a request is sent and a response is awaited, the overarching nature of the entire AJO journey remains resolutely asynchronous.
• By design, AJO explicitly avoids blocking its progression or polling your external system for the eventual completion of the requested action.

[Michael_Soprano]

So AJO Custom Action node will wait for response (lets say few seconds) or it progresses automatically to the next node right away?

[SatheeskannaK · Accepted solution]

@Michael_Soprano By default, the AJO will wait approximately 30 seconds for an API response before proceeding to the next node. This duration can be adjusted if needed.

Have a look at this page,

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/connect-systems/external-systems/....