Skip to content
Browse Help

Categories

On this page
  1. Open automation activity
  2. Check current configuration
  3. Read recent activity
  4. Understand communication states
  5. Read survey evidence separately
  6. Find why a survey was not sent
  7. When there is no activity
  8. Actions that are not available here

Automation Activity & Diagnostics

3 min read

Understand current readiness, recent runs and why a survey was not sent.

Automation Activity helps you distinguish how an automation is configured now from what ELUNIA recorded when recent survey work became due.

Open automation activity

  1. Open Surveys from the main menu.
  2. Open Automatic survey sending.
  3. Find the automation you want to inspect.
  4. Select View activity.

Use Edit current configuration when you need to change the rule. The Activity page itself is read-only.

Check current configuration

The Current configuration section shows the automation’s Property, Survey, scheduled trigger, minimum stay, reminder setting and current active state.

A warning appears when the automation is currently paused, the property currently uses manual sending, or the selected survey is currently inactive. These warnings describe readiness now. They do not prove what the settings were when an older activity entry was created.

Read recent activity

Each row in Recent activity represents a saved due occurrence. It identifies:

  • The Guest and Stay
  • Whether the occurrence is Initial or Reminder
  • When it became due
  • The activity state
  • Related invitation, communication and response evidence

Use the available actions to open the Guest, Stay, Communication or completed Response. These links open the original authorized ELUNIA records.

Understand communication states

  • Due / Processing: ELUNIA saved the occurrence, but there is not yet matching communication evidence.
  • Queued: the communication is waiting for the protected sending workflow.
  • Sending: ELUNIA has claimed it for a delivery attempt.
  • Sent: the provider accepted the message. This does not prove inbox delivery.
  • Delivered: the provider reported delivery.
  • Skipped: ELUNIA recorded a known reason not to send it.
  • Failed: delivery could not complete safely.
  • Bounced: the recipient’s email server rejected it.
  • Spam complaint: the recipient reported it as unwanted.
  • Suppressed: ELUNIA or the provider prevents delivery to this recipient.

Read survey evidence separately

Communication delivery and survey behavior are different evidence.

  • Opened means the guest opened the survey link. It does not mean ELUNIA tracked an email open.
  • Completed means ELUNIA has a completed survey response.
  • No invitation recorded means the occurrence has no matching invitation record available.

A row may correctly show Communication: Delivered and Survey: Completed at the same time.

Find why a survey was not sent

  1. Open the automation’s Activity page.
  2. Find the Guest and Stay in Recent activity.
  3. Read the customer-safe reason shown for a Skipped or Failed state.
  4. Open the related Communication for its canonical delivery details.
  5. Follow the displayed guidance, such as correcting the guest email, activating a usable message template, or reviewing suppression.

ELUNIA may explain known conditions such as a cancelled stay, invalid guest email, unavailable survey or automation, missing initial invitation, missing active message template, an already received response, an ineligible invitation, recipient suppression, bounce, provider failure or exhausted retry policy.

When there is no activity

No activity yet means no due occurrence has been saved for that automation. Absence alone cannot establish a historical reason. It does not prove that the rule was paused, the stay was cancelled, a minimum-stay condition failed, commercial access was unavailable or the scheduler missed work.

Review the current configuration for present readiness. Contact Support if you have a specific eligible stay and expected due time that needs investigation.

Actions that are not available here

Automation Activity does not resend a communication, retry a background job, edit occurrence history or change the original evidence. Use the existing approved Communication workflow for available operational actions.

Was this article helpful?

Still need help?

Need more help? Sign in to contact Support.

Sign in