Function Compute's retry behavior depends on how you invoke your function. Synchronous invocations never retry automatically. Asynchronous invocations retry automatically for certain error types, with configurable behavior and billing implications that vary by error.
Synchronous invocations
Function Compute does not retry failed synchronous invocations. If a synchronous invocation fails, retry from your client code.
Asynchronous invocations
The following table describes how Function Compute handles failed asynchronous invocations.
| Error type | Retry behavior | Billed | Resolution |
|---|---|---|---|
HandledInvocationError and UnhandledInvocationError | Retries up to 3 times by default. Adjust the retry count to match your business requirements. | Yes — billed per invocation. See Billing overview. | Fix the error in your function code. |
| Concurrency limit exceeded | Retries for up to 5 hours using exponential backoff. The first retry starts 0.5 seconds after the failure; subsequent intervals double (1 s, 2 s, 4 s, 8 s, …). | No | Increase your concurrency quota in Quota Center. By default, each Alibaba Cloud account can run up to 100 instances per region. |
| Internal error | No retry | No | Contact technical support via DingTalk (group ID: 64970014484). |
| Insufficient Function Compute resources | No retry | No | — |
What's next
Contact us if you encounter problems when using Function Compute.
该文章对您有帮助吗？