Run
Usectx.run
to safely wrap any non-deterministic operation, like HTTP calls or database responses, and have Restate store its result in the execution log.
ctx.run
, you cannot use the Restate context (e.g., ctx.get
, ctx.sleep
, or nested ctx.run
).
Asynchronous run actions
Asynchronous run actions
To run an action asynchronously, use You can use this to combine your run actions with other asynchronous operations, like waiting for a timer or an awakeable.Check out Concurrent tasks.
ctx.runAsync
:Serialization
Serialization
Have a look at the serialization docs to learn how to serialize and deserialize your objects.
Error handling and retry policies
Error handling and retry policies
Failures in
ctx.run
are treated the same as any other handler error. Restate will retry it unless configured otherwise or unless a TerminalException
is thrown.You can customize how ctx.run
retries via:- You can limit retries by time or count
- When the policy is exhausted, a
TerminalException
is thrown - See the Error Handling Guide and the Sagas Guide for patterns like compensation
Increasing timeouts
Increasing timeouts
If Restate doesn’t receive new journal entries from a service for more than one minute (by default), it will automatically abort the invocation and retry it.However, some business logic can take longer to complete—for example, an LLM call that takes up to 3 minutes to respond.In such cases, you can adjust the service’s abort timeout and inactivity timeout accommodate longer execution times.For more information, see the error handling guide.
Deterministic randoms
The SDK provides deterministic helpers for random values — seeded by the invocation ID — so they return the same result on retries.UUIDs
To generate stable UUIDs for things like idempotency keys:Random numbers
To generate a deterministic float between0
and 1
:
Random
class but is deterministically replayable.
You can use any of the methods of java.util.Random
to generate random numbers: for example, nextBoolean()
, nextLong()
, nextFloat()
, etc.