Documentation

Operational logs

Use task-trigger, user-event and workflow-specific logs to investigate a problem.

Open Logs → Audit trigger log or User Event Log. Choose the log matching the operation instead of assuming every action is recorded in one place.

Audit trigger log records task-generation attempts with their trigger/template, start time, status and log text. Check InProgress, Success or Error and the details before retrying a policy. A successful trigger attempt is not evidence that a staff member completed the resulting task.

User Event Log records supported user operations and can link to a hotel, room or reservation. Check Start (UTC) versus Start (Hotel Time) when comparing entries with a front-office report. Inspect progress and error details. Stop, where available, requests that the running operation stop; it is not a rollback of work already saved.

Other workflows have dedicated history:

WorkflowWhere to inspect
Reservation importPreferences → Import Log
Guest telephone assistantAI → Phone Line → Phone Log
Outbound messagesMessenger → Message
Staff push deliveryNotifications → Notification Delivery Attempt
Attendance intake/reconciliationAttendance → Attendance Event Log / Attendance Anomaly

Give support the operation, hotel, time zone, approximate time and a redacted error. Logs may contain personal details or technical configuration; do not export an entire record set when a small redacted example is enough. Retention varies by log, so older entries may no longer be available.

StayLuma.ai · Documentation