Trace Details
Click on any row in the trace list to open the full detail view. This page gives you the complete record of a single communication event — what was sent, what was received, and whether it succeeded.
Overview Panels
The top of the trace detail page shows three panels:
Overview
| Field | Description |
|---|---|
| Timestamp | Exact date and time of the communication |
| Type | Flow type (e.g. MOZREST TO POS, RMS TO MOZREST) |
| Direction | OUTBOUND (Mozrest sending) or INBOUND (Mozrest receiving) |
| Status Code | HTTP response code (200 = success, 4xx/5xx = error) |
| Duration | Total time for the request/response cycle |
Context
Shows the Venue, RMS, and POS system involved in this trace.
Metadata
Shows the Order ID, Check Number, and Reservation ID associated with the trace. Use these to cross-reference with your RMS and POS records.
Request Details
The full outbound or inbound API call:
| Field | Description |
|---|---|
| Method | HTTP method (e.g. POST, PUT) |
| URI | The endpoint URL that was called |
| Headers | HTTP headers including authentication tokens and content type |
| Body | The full JSON payload (e.g. guest name, table ID, party size, contact details) |
Response Details
What the receiving system returned:
| Field | Description |
|---|---|
| Status Code | HTTP status code |
| Response Body | The data returned by the receiving system |
| Error Details | If failed, the error message is highlighted for easy identification |
Identifying Failures
When a trace fails, the detail view shows:
- The HTTP error code (e.g. 500 Internal Server Error, 400 Bad Request)
- The full error message from the receiving system, highlighted in red
- The request payload that caused the error — so you can see exactly what was sent
Common RMS-side failure patterns
| Symptom | What to check |
|---|---|
| Trace shows RMS → Mozrest as FAILED | Your endpoint returned an error. Inspect the response body for the error message. |
| No Mozrest → POS trace exists after your event | Mozrest may not have received the event, or it failed validation. Check the RMS → Mozrest trace for errors. |
| Mozrest → POS trace shows FAILED | The POS rejected the request. Inspect the POS error response — common causes: table not found, venue not configured, invalid payload. |
| Mozrest → RMS trace shows FAILED | Mozrest tried to send POS data back to you but your endpoint returned an error. Check your webhook endpoint is responding. |
Use Cases
During Integration (Sandbox)
- Verify your webhook sends are received by Mozrest (RMS → Mozrest flow).
- Confirm Mozrest forwards the correct payload to the POS (Mozrest → POS flow).
- Validate the POS responds with the expected data.
- Debug any failures before accreditation.
In Production
- Monitor ongoing communication health.
- Quickly trace a specific reservation when a venue reports an issue.
- Determine whether a failure occurred on the RMS side, Mozrest side, or POS side.
- Gather trace evidence when collaborating with Mozrest support.