⏱ Estimated time: 3 minutes
👤 Role: Reservations Managers, IT Support, Receptionists, Spa Managers
How to access the technical history of an individual transaction.
How to identify why a booking failed to reach your PMS or Spa system.
Common error codes and how to interpret them.
Use the Error Log whenever you encounter an "In Progress" order that hasn't moved to "Complete," or if a guest has a confirmation from the platform but the booking is missing from your internal diary (Opera, Guestline, Premier, etc.).
Key Logic:
The platform acts as a bridge between the guest and your internal systems. If that bridge "breaks" due to a timeout, a configuration error, or a mapping issue, the platform records the exact technical reason in the Error Log. Reviewing this log is the first step in troubleshooting any integration failure.
Have the Order Number or Guest Name ready.
Ensure you have "Admin" or "Manage" permissions to view order details.
Log in to the Ecommerce platform.
Click Orders in the left-hand sidebar menu.
Use the search field to find the order you wish to investigate.
Click the Edit button on the right-hand side of the order row.
Once inside the order details, look at the sub-menu on the left-hand side.
Click on Error Log.
You will see a chronological list of communication attempts between the platform and your third-party systems.
The "In Progress" Audit: If an order has an error log entry but the guest has successfully paid (checked via the Payments tab), the booking is valid but "Ghosted." You must manually create the reservation in your PMS to ensure the guest has a room or treatment upon arrival.
Read the Full String: Error messages can look like long strings of code. Look for keywords like 504 Gateway Timeout, Authentication Failed, or Invalid Room Code. If you are unsure what a specific error means, take a screenshot and send it to support@journey.travel for technical assistance.