golem-schedule-future-call-rust

Use the schedule_ variant of any method on the generated agent client, passing a Datetime as the first argument. For example, counter.schedule_increment(Datetime { seconds: now_secs + 60, nanoseconds: 0 }) runs the increment 60 seconds later.

Datetime comes from golem_rust::wasip2::clocks::wall_clock and represents a point in time as seconds plus nanoseconds since the Unix epoch. You construct it with a seconds field and a nanoseconds field for sub-second precision.

No, scheduled invocations return immediately after enqueueing the call. The target agent processes the method when the scheduled time arrives, so the caller is never blocked waiting for execution.

Yes, scheduled variants accept the same arguments as the original method along with the Datetime. For example, reporter.schedule_generate_report("summary".to_string(), Datetime { ... }) passes both the argument and the scheduled time.

Common use cases include periodic tasks that reschedule themselves at the end of each run, delayed processing after a cooling-off period, timed reminders and notifications, and retrying failed operations with backoff delays.