In IBM API Connect, the sequence of execution for global policies and API assembly is crucial, especially in cases where the process fails. If the process fails while executing the post-request, the execution order is as follows:

Pre-request global policy: This is the first to execute before the API request is processed.

API assembly: After the pre-request global policy, the API assembly (which contains the core business logic of the API) is executed.

Post-request global policy: This is executed after the API assembly has been processed, but if the process fails here, the post-request global policy may not complete.

Error global policy: When the failure occurs, the error global policy is triggered to handle any errors that occur during the execution of the API, specifically after the failure in the post-request.

Thus, if a failure occurs in the post-request global policy, the subsequent step would involve invoking the Error global policy to handle the failure. The execution order is as follows:

Pre-request global policy

API assembly

Post-request global policy (failure occurs here)

Error global policy

This is the correct flow based on API execution steps in the presence of global policies.