If your after registration webhook has response.parse set to false, the webhook is considered non-blocking or asynchronous. In this configuration, Ory ignores the response from your webhook, so you do not need to return any specific payload or status code for Ory to consider the webhook successful. The system will not process or interpret the response, and the registration flow will continue regardless of what your webhook returns. You can simply return a standard HTTP 200 OK or 204 No Content, but even if you return a different status or body, Ory will not act on it when response.parse is false. This is useful for integrations where the outcome of the webhook does not affect the registration process, such as logging or sending data to analytics platforms. > If you decide that the system response that indicates if the process was successful is not critical for your setup, make the webhook execution non-blocking to ignore whatever response is returned. To do that, set response.ignore to true in the webhook config. > — [Webhook response handling](https://www.ory.sh/docs/guides/integrate-with-ory-cloud-through-webhooks#webhook-response-handling) So, in summary: with response.parse: false, you can return any response, but Ory will ignore it and proceed with the registration flow.

Based on the knowledge sources provided, if your after registration webhook has response.parse set to false and returns a 200, Ory should ignore the webhook response and proceed to the next hook (such as the session issuer). However, there are known issues where the order of hooks—especially the session hook—can interfere with the execution of other hooks. Specifically, if the session hook is not the last in the list, it can prevent subsequent hooks from executing, or cause unexpected behavior such as "aborted registration hook execution." The documentation and multiple GitHub issues highlight that the session hook modifies the HTTP response, and no other hooks are executed after it. Therefore, it is critical to ensure that the session hook is always the last in your after registration hooks list. If it is not, you may encounter errors or hooks not being triggered as expected: > Because the session hook modifies the HTTP response, no other hooks are executed after it. If you want to execute other hooks besides the session hook, you need to make sure that it is executed last. > [Troubleshoot Ory Actions Webhook issues](https://www.ory.sh/docs/troubleshooting/troubleshoot-actions) This is further confirmed by community and team responses: > The session hook overwrites any other hooks that run after it which is why you don’t see a response. ... The solution would be to put the session hook after the other one. > [GitHub Issue #361](https://github.com/ory/network/issues/361) So, if you are seeing "aborted registration hook execution" after your webhook (even with a 200 response), check your configuration and ensure the session hook is the last in the list of after registration hooks. If the order is correct and the issue persists, there may be another misconfiguration or a bug, but the knowledge sources do not provide further troubleshooting steps for this specific error message.

Your configuration shows two web_hook hooks (one with response.parse: true and one with response.parse: false), followed by the session hook. This order is correct according to Ory’s documentation and community guidance: the session hook must always be last, as it modifies the HTTP response and prevents any subsequent hooks from running [Troubleshoot Ory Actions Webhook issues](https://www.ory.sh/docs/troubleshooting/troubleshoot-actions), [Sign in after registration](https://www.ory.sh/docs/actions/session). Here’s what your config achieves: - The first web_hook (parse: true) is a pre-persist (flow-interrupting) hook. Ory will parse the response and can interrupt the flow if your webhook returns a 4xx/5xx status or a specific payload. - The second web_hook (parse: false) is a post-persist (non-blocking) hook. Ory will ignore the response, so you can return any status (typically 200 or 204), and the flow will continue. - The session hook is last, which is required for correct execution. If you are still seeing errors like "aborted registration hook execution," double-check the following: - The first (parse: true) webhook must return a 2xx/3xx status for the flow to continue. Any 4xx/5xx will interrupt the flow [Webhook response handling](https://www.ory.sh/docs/guides/integrate-with-ory-cloud-through-webhooks#flow-interrupting-webhooks). - The second (parse: false) webhook’s response is ignored, so it should not affect the flow. - The session hook is last, as required. If all of the above is correct and you still encounter issues, the knowledge sources do not provide further troubleshooting steps for this specific scenario. In that case, you may need to review your webhook endpoints for unexpected errors or consult Ory support for deeper investigation. Summary: Your hook order is correct. Ensure your pre-persist (parse: true) webhook returns a 2xx/3xx status, and the session hook remains last. If issues persist, the knowledge sources do not provide more specific guidance.