# Retry policies ### Webhooks Webhooks expect an HTTP 2xx response to be considered delivered. By default, we will attempt delivery 5 times before marking a webhook as failed using an exponential back-off algorithm. Failed webhooks can still be collected from the /webhook/poll endpoint. Webhooks adhere to an at-least-once delivery policy. This means that we will potentially retry even if your app acknowledges receipt (e.g, if network conditions prevent the request completing, for example). ### Tasks Workflow Task Runs will be retried if they do not return a valid success or error response. While this is handled for you with native tasks, if deploying serverless functions within your own account or using embedded JS tasks, you must always return appropriately to avoid retries. Should we see a retry level >30%, we will disable your Task Runs and this will render all related Workflow Runs inoperable also. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.wundaflow.com/core-concepts/retry-policies.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.