Jobs and events · rule
subscriber.run_invalid
Subscriber's run: isn't a call of an action in its own domain.
Area 12, Jobs and events; not declinable; the next step is usually the agent's.
run: calls the action:
type Note = Text { max_length: 200}entity Reminder { id: Uuid note: Note sent: Bool policy: { create: [Access.authenticated] read: [Access.system] update: [Access.system] }}type ReminderDue = Event { reminder_id: Reminder.id}action send_reminder(reminder_id: Reminder.id) fails ReminderNotFound -> Unit { attempt Reminder.update(reminder_id) { set: { sent: true } }}subscriber send_due { on: ReminderDue run: send_reminder}
error: `run: send_reminder` isn't a call --> main.jadpo:31:10 |31 | run: send_reminder | ^^^^^^^^^^^^^ not a call reason: `run:` calls one action of the subscriber's own domain, passing the event or its fields; all the logic lives in the action. next: Write `run: <action>(event)` (agent) rule: subscriber.run_invalid help: https://jadpo.dev/docs/errors/subscriber.run_invalidcheck failed: 1 error, 1 file
Markdown for agents: /docs/errors/subscriber.run_invalid.md.Built from Jadpo main at a707efb.