What is a scheduled transaction?

A scheduled transaction is a transfer you create now to run at a time in the future. Until that time it is not applied. When the clock hits, it enters the same lifecycle as any other transaction and can apply, hold, or reject.

How does a scheduled transaction work?

You send the same fields as a normal transfer, plus a future time. The ledger stores it and waits. At that time the worker picks it up. The scheduled record is the parent of the executed one. Your reference still has to be unique.

Scheduled vs queued vs inflight

Queued means accepted and waiting for the worker, usually seconds. Scheduled means waiting for a clock you set. Inflight means the worker already ran and the money is held for commit or void. Do not use schedule as a hold. Use inflight.

What happens if funds are missing later?

The scheduled transfer still runs. If the source cannot pay, it rejects like any other transfer. Check available funds before you schedule, or accept that some scheduled work will fail and listen for the webhook.

In Blnk, scheduled transactions show as scheduled until the time you set, then they follow the normal lifecycle. The schedule is the parent of the applied or rejected record. See scheduling.