Skip to main content
Lambda ingress is the front door and observability layer for CargoWise outbound deliveries. It accepts what CargoWise pushes, records the delivery, and hands it to the correct enabled module. Ingress does not read the CargoWise database or look for documents on its own. CargoWise must send each delivery to the outbound target configured for that module.

​
The shared handoff

Ingress has four jobs:
  1. Confirm that the sender and organization are allowed to deliver.
  2. Capture the event and its source payload.
  3. Identify the configured module lane and validate the delivery for that lane.
  4. Return an acknowledgment after the module handoff is safely recorded.

​
Accepted is not complete

An Accepted ingress event means Lambda captured the delivery and completed the safe handoff for that lane. It does not mean an invoice is stamped or Analytics data is queryable. After acceptance, follow progress in the destination module: Stamping and Analytics use separate CargoWise outbound targets. Sending a delivery to one target does not fill the other module.

​
What the Ingress workspace shows

The Ingress workspace shows the delivery itself: when it arrived, its outcome, its route, retry attempts, parsed messages, payload evidence, and its relationship to module records. Use it when you need to answer:
  • Did CargoWise reach Lambda?
  • Which module lane received the delivery?
  • Was the delivery accepted, rejected, duplicated, or stalled?
  • Which Stamping document or Analytics projection is connected to it?

How ingress works

Follow authentication, capture, XML interpretation, routing, and acknowledgment.

Ingress workspace

Search deliveries, read outcomes, inspect evidence, and follow module relationships.