When Dragon Guard WMS posts a receipt or a shipment, the backend records an outbound acknowledgment and dispatches an HTTP callback to the ERP system connected to your tenant. These callbacks carry a structured payload describing the posted document so that the ERP can react — updating inventory records, closing purchase orders, or triggering downstream fulfillment flows. The Outbound Acknowledgments screen atDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/CodexaCP/DG_WEB/llms.txt
Use this file to discover all available pages before exploring further.
/dashboard/admin/outbound-acknowledgments is the admin-facing log for all of these notifications. It lets you see which callbacks succeeded, which are pending, which failed, and which were intentionally skipped — and it gives you the tools to inspect payloads and retry failed deliveries without reprocessing the underlying warehouse document.
This screen is a monitoring and retry interface only. It does not affect posting behavior, trigger new postings, or reverse any warehouse transactions. The posted document status in Dragon Guard WMS is independent of ERP callback delivery.
Filtering the Acknowledgment List
The list view supports three independent filters that can be combined:| Filter | Values / Description |
|---|---|
| Status | PENDING, SENT, FAILED, SKIPPED |
| Event type | RECEIPT_POSTED, SHIPMENT_POSTED |
| Search text | Free-text match against source document number, posted document number, or event type |
Status Values
| Status | Meaning |
|---|---|
PENDING | The notification has been queued but not yet dispatched. |
SENT | The callback was delivered and the ERP responded with a success code. |
FAILED | One or more delivery attempts were made but all returned an error or timed out. |
SKIPPED | Dragon Guard determined the callback should not be sent (e.g., no ERP URL configured for the tenant, or the event was suppressed by configuration). |
Event Types
| Event | Triggered by |
|---|---|
RECEIPT_POSTED | A warehouse receipt (inbound shipment) was posted in Dragon Guard WMS. |
SHIPMENT_POSTED | An outbound shipment was posted in Dragon Guard WMS. |
Acknowledgment Detail Dialog
Click any row in the list to open the detail dialog. The dialog surfaces all available information about that specific notification:- Summary fields
- Payload and response
| Field | Description |
|---|---|
| Event type | RECEIPT_POSTED or SHIPMENT_POSTED |
| Status | Current delivery status |
| Source document | The originating warehouse document number (pre-posting reference) |
| Posted document | The posted document number assigned by Dragon Guard after processing |
| Callback URL | The ERP endpoint that Dragon Guard attempted to call |
| Attempt count | Total number of delivery attempts made so far |
| Last HTTP response code | The HTTP status code returned by the ERP on the most recent attempt |
| Last error | The error message captured on the most recent failed attempt, if any |
Retry Behavior
Admins can manually trigger a retry for acknowledgments that have not yet reached aSENT status.
Open the acknowledgment detail
Click the row for the acknowledgment you want to retry. The detail dialog will open.
Click Retry
If the acknowledgment is eligible for retry (status is
PENDING, FAILED, or SKIPPED), the Retry button will be active. Click it to enqueue a new delivery attempt.Backend processes the retry
Dragon Guard calls
POST /api/outbound-acknowledgments/{id}/retry. The backend validates eligibility, increments the attempt counter, and dispatches the callback to the ERP URL.The SENT Restriction
If you believe aSENT acknowledgment was received incorrectly by the ERP, investigate on the ERP side using the payload JSON and last response body visible in the detail dialog. Do not attempt to work around the retry restriction by any other means.
API Endpoints
| Method | Endpoint | Purpose |
|---|---|---|
GET | /api/outbound-acknowledgments | List all outbound acknowledgments (supports filter params) |
GET | /api/outbound-acknowledgments/{id} | Retrieve full detail for a single acknowledgment |
POST | /api/outbound-acknowledgments/{id}/retry | Enqueue a retry for an eligible acknowledgment |