Skip to main content

Custom Events

Event variables

Custom events let one stack arrange for another stack to run later. A program has five custom-event slots. Give each event a distinct name, then select it from the scheduling blocks' dropdowns.

Blocks​

when custom event … named … fires

Choose slot 1–5 and a name. Put the actions to run later inside this event. Creating the handler alone does not schedule it.

Event variables

Uses the common event variables. No additional event-specific fields.

schedule custom event … at Unix timestamp

Choose the event and connect a timestamp in seconds. A past date is skipped and any existing schedule remains unchanged. Accepted runs are at least five seconds in the future.

schedule custom event … after

Choose the event and a duration. Delays below five seconds, including zero or negative values, become five seconds.

cancel custom event

Removes the pending occurrence. Keeps the handler so it can be scheduled again.

custom event … is scheduled?

Returns true while a run is waiting, including when due; false after cancellation or when execution starts. If the handler schedules itself again, the new schedule returns true.

There is one pending occurrence per custom event. Scheduling it again replaces that occurrence; it does not append another job. The extra date/time preset in the toolbox is the same scheduling block prefilled for a relative date.

Example: a replaceable reminder​

  1. Add custom event 1, name it Reminder, and put send notification inside it.
  2. Add a GUI button named Remind me later.
  3. In the button, schedule Reminder after duration 30 minutes.
  4. Add another button that cancels Reminder.

Pressing the first button again moves the reminder to 30 minutes after the latest press. Use is scheduled? as the cancel button's visible condition if you only want that control shown while a reminder is pending.

Repeating work​

For a regular cadence, prefer the interval or weekly blocks in Events. A custom event can schedule itself again, but long-running chains are subject to server safety limits. Avoid short self-scheduling loops and use a variable or condition to stop deliberate chains.

Inspect the scheduled-events display and execution log when a run seems late or missing. Server execution and device delivery are separate; a scheduled device action still needs its device prerequisites.