Three observations that deserve different status labels
- The schedule was created
- This establishes the existence of a scheduling workflow, not delivery of the HBAR amount to the exchange. Keep the creation record available, but ask for the state of the scheduled transfer itself when the question concerns exchange funding.
- The required signatures were collected
- The current Hedera documentation distinguishes immediate execution after sufficient signatures from wait-for-expiry behavior. In the latter mode, signatures can be ready while the scheduled transaction still waits. Establish which mode was selected before interpreting a colleague’s message saying everyone has signed.
- The scheduled transfer executed
- Execution needs its own verified outcome. Read the transaction result and intended HBAR transfer, rather than treating a status on the signature-collection screen as a complete payment receipt. A scheduling record and the resulting transfer are related evidence with different jobs.
Look at the execution policy before diagnosing a delay
Hedera’s scheduled-transaction guide documents wait_for_expiry as an option. When enabled, the transaction is evaluated for execution at its expiration time instead of executing as soon as enough signatures arrive. The guide also describes execution after expiry as best effort at an available consensus time; a local clock crossing that time is not a receipt.
In a fictional team purchase, the finance colleague finishes signing at 11:00 while the schedule is set to wait until later. An exchange enquiry saying payment completed at 11:00 would skip the unresolved execution stage. Record signatures complete and transfer pending separately. Do not turn the scheduled amount into an already-paid input merely because internal approval is finished.
A short status sheet for the person arranging the exchange
| Question | Evidence to request | Status to avoid assuming |
|---|---|---|
| Which execution mode applies? | The schedule’s current configuration | Immediate execution by default in every case |
| What stage is complete? | Signature and execution states separately | Signed means paid |
| Did the required HBAR arrive? | Executed transfer result and recipient details | Schedule creation means funding |
| Can the ETH receipt now be checked? | The exchange record after funding is established | A future payment already triggered payout |
Do not schedule around an unverified exchange deadline
Before relying on a future payment, check the current funding instruction and its timing requirements. The blockchain schedule does not by itself extend an exchange’s payment conditions or preserve an old estimate. If the schedule was arranged before those conditions were reviewed, clarify compatibility through the responsible party instead of promising a payout time.
If funds have already moved, provide the actual transfer reference and explain which earlier message referred only to signatures. If they have not, resolve the schedule first. Never send a second HBAR payment solely to compensate for an approval screen that was mistaken for a receipt; first establish the original transfer’s state.
Scheduled HBAR payment questions
- Can all signatures be present while a scheduled transfer is still pending?
- Yes, when wait-for-expiry mode applies. Check the execution policy and actual outcome.
- Does the scheduled time guarantee an exact ETH payout time?
- No. Schedule execution and an exchange payout are separate stages with separate conditions.
- Does creating a schedule pay the exchange?
- Not by itself. Verify the required HBAR transfer and its result.
- Should I send another payment because a signed schedule has not executed?
- First resolve the original schedule and transfer state. A signatures-complete message is insufficient evidence for another payment.
Current Hedera documentation
Reviewed: