Documents and notifications support operational work through their own records and processing paths. Their state is separate from the order, booking or resource they concern.
Document records and content
ShowMgr supports documents associated with orders and resources. A document record holds information such as title, description, group, type and its record association. It can refer to uploaded file content or a hyperlink.
Document retrieval supports Amazon S3 and Azure Blob Storage. Storage settings select the primary provider, and the retrieval path includes fallback handling between providers.
| Observation | Meaning | Next area to examine if there is a problem |
|---|---|---|
| A document appears in a list | The document record is being returned | Its content-retrieval path |
| A file opens | Retrieval succeeded for that request | The affected user's access if another user cannot open it |
| A hyperlink is present | The record points to a linked destination | Access and availability at that destination |
| An order opens | The operational record is available | The document association, metadata and content |
A listed document and a retrievable file are different parts of the workflow. A content-retrieval failure does not necessarily mean that the document record or its associated order is missing.
Notification processing
Booking alerts and push-notification requests can be submitted to Amazon SQS for processing. The triggering operation and notification settings determine whether alerts are requested.
Queue submission, processing and recipient delivery are separate events. Saving a booking establishes the operational change; it does not confirm that a recipient has received a notification.
Some booking update operations include a send-alerts option. Different changes can therefore produce different notification behavior even when they affect the same booking.
Investigate a notification issue
Identify the booking, the action that triggered the notification, the applicable rule and the intended recipients. Then review the processing and delivery information for that request.
Distinguish a notification that was not requested from one awaiting processing or one that failed during delivery. The booking's saved state alone cannot distinguish those conditions.
Investigate a document issue
Identify the document ID and its associated order or resource. Determine whether the record contains an uploaded file or a hyperlink, identify the affected user and capture the retrieval error.
Use the document identity when comparing results. A filename is a label and can be shared by more than one document record.