Automation eligibility

Eligibility has two stages: whether a Stay is considered before an occurrence exists, and whether communication remains possible after a stage is due.

Before an occurrence

The scheduled processor considers only active Automations for Properties in Automatic sending mode whose organization can send and has the Automations entitlement. The Survey must still be Active. The Stay must belong to the same Property and meet Only for stays of at least. Check-out anchors consider Checked out Stays; booking and check-in anchors consider Upcoming, Checked in and Checked out Stays. Cancelled Stays are not sent.

From the left sidebar, select Automations, select View activity, and use the status/date filters. ELUNIA does not historically persist every candidate rejected before an occurrence. Therefore no activity row does not prove a specific reason. Check configuration and Stay facts directly.

After a due occurrence

ELUNIA applies downstream safeguards while creating the Communication: valid Guest email; active same-Property Survey and Automation; active message template for a usable Survey language; and, for reminders, an initial Invitation/token. These failures become Skipped communication evidence where processing reached that point. At send time, subscription access is checked again; completed/revoked/expired invitations or a paused Automation make a reminder Skipped, while a suppressed recipient becomes Suppressed.

Skipped is a deliberate non-send, not a provider failure. Failed means an attempted delivery path could not complete or exhausted safe retries.

Other boundaries

An active provider mapping is authoritative for its Stay data, but integration-managed Stays use the same eligibility engine. PMS synchronization is not Automation execution. Automation never changes status or dates.

If a Stay should qualify, check in order: Property sending mode, plan/access, Automation and Survey state, Property ownership, status/anchor, dates/timezone, nights, Guest email, usable locale and active invitation/reminder template. Then use Delivery Activity for downstream evidence or contact Support with record references and no unnecessary personal data.