# `schedule.run_invalid`

Schedule's `run:` isn't a call of an action in its own domain with no arguments.

Area 12, [Jobs and events](../topics/jobs-and-events.md); not declinable; the next step is usually the agent's.

`run:` calls an action of the schedule's own domain with nothing; the time is `clock.now`, fixed for the run:

```jadpo
type RemindAt = Instant {}

action remind(at: RemindAt) -> Unit {}

/// Sends the reminders due.
schedule reminders {
    every: 15m
    run: remind(RemindAt(clock.now))
}
```

```text
error: A schedule passes nothing to `remind`
 --> main.jadpo:8:16
  |
8 |     run: remind(RemindAt(clock.now))
  |                ^^^^^^^^^^^^^^^^^^^^^ arguments given
  reason: `run:` calls one action of the schedule's own domain with no arguments; the action reads `clock.now`, fixed for the run, and queries for anything else, so all the logic lives in the action.
  next: Write `run: remind()`, and let `remind` read `clock.now` and its queries for what it needs (agent)
  rule: schedule.run_invalid
  help: https://jadpo.dev/docs/errors/schedule.run_invalid

check failed: 1 error, 1 file
```