> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jaantonio.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Workspace
> Search CargoWise deliveries, read ingress outcomes, and inspect their module relationships.
The Ingress workspace is a technical inspection surface for CargoWise deliveries into Lambda. Use
it to confirm what arrived and where it went. Continue the actual business work in Stamping or
Analytics.
## Find a delivery
1. Search for an exact CargoWise key or event ID.
2. Filter by outcome or enabled module when the list is busy.
3. Turn on **Internal** only when you need events that are not linked to a product module.
4. Select a row to open its delivery details.
**Live** mode applies new event changes automatically. Switch to **Paused** when you need the current
list to stay still during an investigation. Use **Refresh** for an immediate update.
## Read the event list
| Column | What it tells you |
| ------------ | ------------------------------------------------------------- |
| **Time** | When Lambda received the delivery, shown in Mexico City time |
| **Subject** | The recognized document or shipment and its CargoWise key |
| **Status** | The delivery outcome at Lambda ingress |
| **Module** | The module lane associated with the event |
| **Attempts** | How many times CargoWise delivered the same route and payload |
Retry attempts for the same route and payload appear as one chain. The accepted attempt is shown
when one exists; otherwise the newest attempt is shown.
## Read an outcome
Ingress outcomes describe the delivery handoff, not the final module result.
| Outcome | Meaning | Next inspection point |
| ---------------- | ------------------------------------------------------------------------ | -------------------------------------------------------- |
| **Accepted** | Lambda captured the delivery and completed the lane's safe handoff | Open the product relationship and continue in the module |
| **Duplicate** | The same route and payload were already accepted | Open the accepted delivery linked in the detail panel |
| **Rejected** | Lambda could not safely accept the input, organization, module, or route | Read the response and parsed-message detail |
| **Pending** | The ingress request has not finished finalizing | Leave Live on or refresh after a short wait |
| **Stalled** | The event has remained Pending for at least five minutes | Give support the event ID |
| **System error** | Lambda hit an infrastructure or processing failure during ingress | Give support the event ID and response detail |
| **Unavailable** | Historical evidence does not contain a reliable delivery outcome | Use the remaining payload and relationship evidence |
An Accepted Stamping event can still have a document in **Received** or **Processing**. An Accepted
Analytics event can still be waiting for projection. Follow the linked module record for that work.
## Inspect event details
Select an event to see:
* the receiving route and HTTP response
* payload size, storage state, and SHA-256 checksum
* the linked Stamping document or Analytics projection state
* parsed message types, CargoWise keys, and classifications
* the accepted delivery for a retry chain
The **Product relationship** section is the handoff from ingress evidence to module work. When a
Stamping document is linked, open it from that section to continue in its timeline.
## Download the source XML
Use **Download XML** when you need to compare Lambda's evidence with the source CargoWise delivery.
The checksum in the detail panel identifies the exact captured payload.
Downloaded XML can contain customer, accounting, shipment, and contact data. Store and share it
only through approved support channels.
Return to the shared CargoWise delivery model.
Review capture, XML interpretation, routing, and acknowledgment.
Follow an accepted accounting document through Stamping.
Follow an accepted Analytics delivery into reporting.