Integration Core · checked 2026-10-15
Incoming Records keeps what the other system sent, exactly as it arrived, before anything was done with it. To act on one, find its record on Integration Activity — that record's own state and banner say what to do.
The Incoming Records list
Open it from the Hub's Day to Day card. Each row's chip shows its state in the Hub's words (see State). A System Manager also finds Erase personal data and Erase personal data even if unfinished here, in Actions (Personal data).
The arrival
What arrived, and through which connection. Every field on this form is set by the system.
| Field | What it is |
|---|---|
| Connection | the connection it arrived through |
| Source | Webhook (pushed by the other system), Poll (found by checking), Manual (entered by hand) or Backfill |
| Topic | what the other system called this message, where it names one |
| Record Type in Connected System | what the other system calls this kind of record |
| ID in Connected System | the other system's ID, compared as text; an ID of 0 is a real ID |
| Operation | what happened to the record there: Create, Update, Delete, Cancel, Refund and others |
Timing
| Field | What it is |
|---|---|
| Received At | iVendNext's clock, at the moment it arrived |
| Timestamp in Connected System | the other system's time, used only to put changes to the same record in order — never an age |
| Delivery ID | identifies this delivery; a repeat carries a new one |
| Signature Verified | whether what arrived passed a signature check; a poll does not |
| Repeat Deliveries · Last Repeat Delivery | see below |
| Test Record | made by a certification run, never counted as real activity |
Repeat Deliveries
How many times the same message arrived again, and when the last one came. A repeat adds to the count; it never makes a second record. Repeats arriving at the same instant are not all counted.
State
| Field | What it is |
|---|---|
| Status | its state; the chip says it in the Hub's words |
| Tries · Latest Try | how many tries it has had, and the newest one on Integration Activity |
| Error | the most recent reason; the full history is on the tries |
| Replaced By | on an older arrival, the newer one that replaced it |
The chip reads In progress, Waiting, Set aside, Reversal not confirmed, Needs a decision, Unverified, Skipped or Replaced (a newer arrival replaced it), or else its stored state: Applied, Failed, Cancelled, Superseded or Ignored. They mean what they mean on Integration Activity; this form has no buttons of its own.
Technical details
Folded away, for support: Summary Status, Duplicate Check ID (a second copy of the same change is refused), Content Check Version and Content Check Value, and — for an Integration Manager or a System Manager — Received Content and Received Headers, what arrived, and who erased personal data and when.
What is kept, and for how long
The full message and its headers are cleared 30 days after they arrive once the arrival is finished (Applied, Cancelled, Superseded, Skipped or Ignored). An arrival that is waiting, failed or unsettled keeps them, because they may be the only copy. Its Error is not cleared. A System Manager can erase one person's data sooner (Personal data).