Skip to main content
Restate handles retries for failed invocations.
Check out the Error Handling guide to learn more about how Restate handles transient errors, terminal errors, retries, and timeouts.

​
Retry strategies

By default, Restate does infinite retries with an exponential backoff strategy. Check out the error handling guide to learn how to customize this.

​
Terminal Errors

For failures for which you do not want retries, but instead want the invocation to end and the error message to be propagated back to the caller, you can throw a terminal error. You can throw a TerminalError with an optional HTTP status code and a message anywhere in your handler, as follows: 
return restate.TerminalError(fmt.Errorf("Something went wrong."), 500)
You can catch terminal errors, and build your control flow around it.
When you throw a terminal error, you might need to undo the actions you did earlier in your handler to make sure that your system remains in a consistent state. Have a look at our sagas guide to learn more.