Glossary — every word the Hub shows
Integration Core help · for everyone · graded against Core v1.0.0-rc.5 · written 2026-10-06 · re-read against rc.8's screens 2026-10-09 · words read from the rc.5 tag; rc.6, rc.7, rc.8 and build 2.0.0.157 in the last section
Every state, tile, link, coloured word, button and field the Integrations Hub shows, in its exact words at Core
v1.0.0-rc.5, with each count's honest limit where one is recorded. The last section lists what reads differently on
newer releases.
What this page restates, and from where: the words themselves are read from the rc.5 tag's screens. Their meanings restate the setup guide, Steps 1, 6 and 7 and The things you can press (2026-09-27); the support runbook §2, §3, §3b and §5 (2026-09-13, re-looked-up 2026-10-02); and the known issues §3 and §5 (2026-10-02). Each section ends with its source line.
The Hub's six tiles
Each tile is a count of something that needs a person; click it to open the rows it counts.
| Tile | Counts | Its honest limit |
|---|---|---|
| Needs a decision | records waiting for a person to decide | — |
| Failed | records that did not go through, need a person, and nobody has acknowledged | does not count Needs a decision or Cannot tell if it arrived rows (each has its own tile) |
| Cannot tell if it arrived | records whose outcome Integration Core cannot confirm (Unverified) | ⛔ never press anything to clear them |
| Money records waiting | every money record not finished and not decided, one per change (the latest try) | a count of records, ⛔ not a sum of money; a sale and its payment both count; two tries racing at one change may both count until the next upgrade |
| Differences | open places where the two systems disagree about a record | — |
| Connections with a problem | switched-on connections that cannot reach their system, were refused the sign-in, stopped part-way, are late, or have not reported yet — each once | counts a connection the moment it is switched on, until its first report; notices a quiet one at the next hourly check — up to an hour late, and never while the scheduler is stopped |
Source: the setup guide, Step 1 (2026-09-27; Hub layout rc.5's); the known issues §3 and §5 (2026-10-02).
The Hub's cards and their links
| Card | Links (rc.5 words) |
|---|---|
| Getting started | 1. Add an Integration Manager · 2. Connect a system · 3. Test it (on its setup page) · 4. Switch it on · 5. Watch the first run |
| Your connections | Connections (the list) · Connection Health (a report: one line per connection) · Cannot reach it · Sign-in refused · Stopped part-way · Switched off · Not checked for over a day · Not reported yet |
| Waiting — clears by itself | Kept while switched off · Held behind an unknown attempt · Waiting on a setup change · Set aside · Waiting on Connected System |
| Day to Day | Integration Activity (every change, one row per try) · Incoming Records (what the other system sent) · Differences · Reversals not confirmed |
| Advanced | Record Links · Sync Positions |
| one card per connector | named for the system, linking to its setup page — a connector adds no tile of its own |
⚠ The card title Waiting — clears by itself is a group name, not a promise: Kept while switched off clears when a person switches the connection on, Held behind an unknown attempt waits on the other system, and Waiting on a setup change needs a setup change. ⚠ Stopped part-way lists only connections whose connector reports it; at rc.5 neither shipped connector does, so empty means none reported. ⚠ Not reported yet lists every switched-on connection that has never reported, including one switched on a minute ago.
A state link opens a short report of exactly the rows that state counts; its title starts iVendNext Integration ….
Source: the setup guide, Step 1 (2026-09-27); the known issues §5, IC-HUB-CARDS-B3 (2026-10-02).
The words on a record
What Integration Activity shows for each record, and the stored state behind it (on the form's Status field). What each means for the business, and what to do, is in How Integration Core works, The states a record can be in.
In progress (Queued · Pending · Retrying · Accepted) · Waiting (Blocked) · Set aside (Deferred) · Reversal not confirmed (Reversal Pending) · Failed (Failed) · Cannot be sent (Failed, a lost document) · Acknowledged (Failed — a lost document or a failure no retry can fix, that a person acknowledged) · Unverified (Unverified — ⭐⭐ we cannot tell whether it reached the other system; not failed, not pending, never retried) · Needs a decision (Needs Decision) · Decided and Ignored (Ignored — closed on purpose, by a person or by the connection) · Applied · Cancelled · Superseded · Skipped (Not Applicable) · Test record.
Summary Status (under Technical details): Unprocessed · Failed · Processed. ⛔ Never reason from it: it reads Failed on an Unverified record too, where nobody presses anything, and Unprocessed on a waiting record a person must fix.
Source: the support runbook §2 and §3 (2026-09-13, re-looked-up 2026-10-02); words read at Core rc.5.
The coloured words on a connection
The Connections list shows the first of these that applies, in this order. System is the connected system's name as its connector declares it (for example Acumatica), else its platform key.
| It reads (rc.5) | Colour | Means |
|---|---|---|
| System refused the sign-in since time | red | the other system refused the credentials at the last check |
| Cannot reach system since time | red | the other system did not answer |
| Switched off | grey | off; changes that arrive are kept |
| Not reported yet | blue | on, never reported, still inside its check interval plus an hour |
| Not reported yet | grey | the same, and that window has passed — overdue |
| Not checked for N min / hours / days | red | it reported before, and has stopped looking for changes |
| Stopped part-way | red | its last run stopped before finishing — only for a connector that reports it |
| Live · checked N ago (or checked just now) | green | on, reporting, and nothing above applies. ⚠ At go-live, trust a record crossing, not this word |
Since is shown in your own time zone.
Source: the setup guide, Step 6 (2026-09-27); the support runbook §5 (2026-09-13); words read at Core rc.5.
The buttons
Open … · Open the fix · Ask a … · Retry · Retry selected · Keep iVendNext Version · Re-check · Acknowledge · Mark resolved · Accept — don't report again unless it changes · Link manually · Make inactive · Switch on · Switch off · Connect a system · Open setup · Email me a daily summary · Stop my daily summary — and, for a System Manager only, Erase personal data and Erase personal data even if unfinished.
What each does, and what it does not do, is in the help page Daily operations, What every button does. Everything an operator is allowed to do is one of these; none edits a field.
Source: the support runbook §4 (2026-09-13); the setup guide, The things you can press (2026-09-27).
Fields worth knowing by name
| Field | Where | Means |
|---|---|---|
| Check Every (minutes) | a connection | how often the other system is checked for changes. When a connection counts as late or overdue, when an Unverified alert fires, and the Cannot reach alert (twice this, never under 150 minutes) are relative to it. The others are not: an unconfirmed reversal or an Accepted record alerts after 4 hours, a Set aside one after 12, a Waiting one after its own setting, Alert If Waiting Over (minutes) (24 hours by default) |
| Lock Timeout (minutes) | a connection | how long a send may hold its lock before an interrupted one is moved to Unverified (30 by default) |
| Live Update Failures | a connection | how many times the other system's live updates have failed. ⚠ On some connectors (WooCommerce) it rises only after updates have already stopped — never read it as an advance warning |
| Interface Version | a connection | the contract version the connector registered with |
| Waiting On | a record | why a waiting record waits |
| Error (Reason on a skipped record) | a record | the record's own account of what went wrong |
| ID in Connected System | a record, an incoming record, a difference, a link | the other system's number for the record |
| Amount Confirmed | a record | the amount the other system reported back for what crossed matched ours. ⛔ Not their final bill |
| Final Bill in Connected System · Final Bill Currency | a record | the other system's final bill, where the connector reports it — shown, never compared. At rc.5 neither shipped connector reports it |
| Amount as Received · Currency as Received | a record | the other system's figure on arrival, where the connector passed it — shown, never compared |
| Decision Note · Decided By · Decided On | a record | what a person decided with Keep iVendNext Version, who and when |
| Repeat Deliveries | an incoming record | how many times the same message arrived again. ⚠ Redeliveries that arrive at the same instant are not all counted (measured: 6 concurrent redeliveries read 0) |
| Times Seen | a difference | how many reconciliation passes reported it while open |
Source: the setup guide, Step 4 and Step 7 (2026-09-27); the support runbook §2, §5 and §11 (2026-09-13); field labels
read at Core rc.5; IC-E2E4-B3 on the tracker for Repeat Deliveries.
Differences: kinds and statuses
Kinds: Field Mismatch (the two values differ) · Missing Ours (the iVendNext record was deleted while its link is active) · Missing Theirs (the connection reported the other record missing) · Multiple Matches · Renamed (renamed in iVendNext) · Link Moved (a sync moved a link) · Manual Mapping Skipped (a hand-made link the sync left alone) · Cancelled in iVendNext (a document the connection had sent was cancelled here).
Statuses: Open · Resolved · Accepted As Is (the list reads Accepted; offered only on Renamed, Link Moved and Manual Mapping Skipped, never on a money record, and holds for 30 days while the values stay the same).
On a Renamed difference the two values are the record's own new and previous names; on a Link Moved one, its new and previous linked records.
Source: the support runbook §3b and §9 (2026-09-13); options read at Core rc.5.
Changed in newer releases
The pages describe Core v1.0.0-rc.5. The words below read differently on v1.0.0-rc.6 (tagged 2026-10-02) or on
v1.0.0-rc.7 (tagged 2026-10-06); rc.8 follows the table. A dash in the rc.7 column means as on rc.6.
| On rc.5 you see | On rc.6 | On rc.7 |
|---|---|---|
| card Waiting — clears by itself | card Waiting | — |
| link and report Waiting on Connected System | In progress | — |
| — | — | a new link on the Waiting card, Waiting, by cause: the Waiting on a setup change records as one line per cause and connection, with a count (Unit MTR not mapped — 2); a connector that passes no cause shows No cause recorded. ⚠ It needs the connector to pass the cause: Acumatica does from its tag v1.0.0-beta.3 (and it needs Core rc.7 or later); WooCommerce does not, at its v1.0.0-beta.3 |
| — | — | a record field Cause of the Wait |
| record field Waiting On, on every record that has one | Waiting On while the record waits; Earlier Hold once it has stopped waiting | the same on the form; the Report view's column is Hold Reason |
| connection System refused the sign-in since time | the same, plus System refused the sign-in since time; it is also unreachable when both apply | on the Connections list the chip leads with how long: 3 hours · Sign-in refused by system (and …; it is also unreachable). The form (the connection refused the sign-in details (since …)) and Connection Health keep their full sentences |
| Cannot reach system since time | the same | list: N min · Cannot reach system |
| Not checked for N … | the same | list: N … · Not checked |
| Live · checked N ago | the same | list: N min ago · Live, or Just now · Live |
| a Hub card link to Connections or Integration Activity — and, by the same code, Differences (not walked) — reopens with your last filters | the lists the Hub links to (Connections, Integration Activity, Differences) open on their own default view | opening one of those three lists directly (the menu, a link) no longer keeps the last tile's filter |
Link manually lists record types as keys (tax_rate) |
the same | the record types in words (Tax Rate) |
| one stuck incoming change can grow one Retrying row per re-presentation | the same | one waiting row per stuck change, until it reaches the attempt limit |
the alert email's subject shows an & as & |
& prints as & |
— |
| the shipped alert-email Notification re-emails a failed send while mail is down | corrected; copy its Subject and Condition into your copy | — |
| a link written after a cancel records no Cancelled in iVendNext difference | recorded (for links written after the upgrade) | — |
| once the connectors are gone, Core's own uninstall goes ahead while record links exist | refused while any record link is active | — |
From build 2.0.0.166 (tag v2.0.0.166, 2026-10-14):
- Help holds 77 answer cards: three are new — A record has not gone through (the bell), Failure Kind and Certification Result — and A record failed, A record cannot be sent, A decision keeps coming back, Answer a record that needs a decision, Delivery Outcome and What is kept, and for how long are re-worded to match the screen.
- Erase personal data also reaches each connection's own copies where the connector declares how; a connection that cannot erase its copies is named in a comment on the record and in the Error Log.
- Nothing else on the screens changes. An ERP connection may send gift-card records (
gift_card) once its connector declares them.
From build 2.0.0.157 (tag v2.0.0.157, 2026-10-09 — the build after rc.8; there is no rc.9):
- Help: these long pages leave the desk. Inside it, help is 74 short answer cards (the Help list, still opened from the Getting started card's Help link), and every Integration Core screen has a button — What does this mean? on a form (on a record, the card for its own state), What is this list? on a list or report (in the "…" menu on a phone) — that opens the card for what it shows. The Help menu leads with that screen's card, then Your daily check, then Help: all answers. The six rc.8 pages and their addresses are gone.
- The Differences follow a person's Connection fence of either shape: fenced for Integration Activity only, they see,
count and act on (Mark resolved, Accept, Erase personal data) only their own connections' Differences. ⚠ An
Integration Activity-only fence still leaves them every connection's Incoming Records (the stored order message
included), Record Links, Sync Positions and the actions on those links, and every connection's name and state on the
Connections list, its Hub tile and the six connection reports (
IC-RELEASE-RC9-B2) — to limit a person to some connections, leave Applicable For empty. - Scheduling an email of an Integration Core report other than Connection Health is refused: "…Email me a daily summary…" says what to use instead; an email of one made before the upgrade is switched off, with a comment saying why.
- A Difference's print shows a
<or>in Reference, Record Type or Which Value as text. - The hourly check also rings has not gone through for a record failing in the middle of a long queue, and moves it to Failed at its last try.
The block below describes rc.8 as it shipped.
From v1.0.0-rc.8 (tagged 2026-10-09): the Getting started card gains a sixth link, Help, which opens the list of these
help pages inside the desk; and the Help menu (top right) on Integration Core's lists, forms, reports and help pages
leads with the help pages for that screen, above the site's own entries. ⚠ On the Hub, and on a report opened before any
Integration Core list, form or help page — the Hub's state links included — it shows the site's own entries only; from the
next screen on, Integration Core's pages are there. A narrow window (a phone; the desk hides the menu below its large-screen width) draws no Help menu at all — open the Hub's
Help link there. Integration
Manager, Integration Viewer and System Manager read them; nobody edits them — each is
made from its file at every upgrade. The screens also read differently on rc.8:
- Report titles are the Hub link's words (Cannot reach it, Sign-in refused, Set aside …), not iVendNext Integration ….
- A record's Error sits in the folded Technical details section. The banner shows its first line — after Error: on a failed record, after Reason: on the others — and Show technical detail opens the rest.
- A decision's banner is one fact per line: Why · Do this (Integration Manager only) · Amount · Record · the open difference recorded for it · Not retried automatically.
- A record whose document was deleted (it reads Cannot be sent) names the document: Item ITEM-0042, the document this change belonged to, no longer exists …
- Delivery Outcome reads Landed: arrived there, even if refused. Never Sent: never left. Unknown: cannot tell. — a Landed send may still have been refused; read the record's Error.
- Form titles are words: Record link: Item ITEM-0001 ↔ 4521 · Incoming order 4521 · eu-web-store · Sync position: Outbound · Product · eu-web-store; an incoming record with no order number yet is titled by the other system's id.
- The Differences list names each row by its kind (Missing Theirs, Field Mismatch …); its Reference column shows the iVendNext record, or the other system's number followed by (ID in Connected System). The desk's own notices (Assign To, a followed document) name a Difference by its kind only — open it to see which.
- A Missing Theirs difference names an iVendNext record only where it has one.
- A split payment's row reads Payment SINV-… · line 2.
- Cause of the Wait is no longer a filter box on Integration Activity (filter it from the sidebar or the filter bar).
- The bell: a line that names the connection uses its display name, and a connection's alert (and its email) goes to the Integration Managers who may see that connection — if none may, to the System Managers.
- A new alert, A money record for system is waiting for its next try: a money record the connection has not tried again for longer than three turns of its own schedule (never under four hours).
- The daily summary email counts only the connections its person may see, whichever way they are fenced (on rc.7 a fence on Integration Activity alone was not honoured by the email). Someone else's summary can be sent or downloaded only by Administrator: "Only the person a daily summary is for, or Administrator, can run it. Sign in as Administrator to send or download someone else's summary."
⚠ Not a change: the words Sign-in refused (a Hub link on rc.5) have stood since rc.2 — a tile until rc.4.
Source: words read at the v1.0.0-rc.5 and v1.0.0-rc.6 tags and at origin/development 181ee4e (2026-10-06), whose
product tree the v1.0.0-rc.7 tag carries unchanged (re-read at rc.7 by IC-RELEASE-RC7, 2026-10-06); the
known issues, Upgrading from rc.5 and §5 (2026-10-02) and Upgrading from rc.6 (2026-10-06); the setup guide, Step 6 and Step 7 (2026-09-27);
the rc.8 block read at origin/development d9a058f (2026-10-09), the tree v1.0.0-rc.8 carries, and walked by IC-HELP-HEADERS-WALK
(2026-10-09); the build 2.0.0.157 block read at origin/development 7b9eab0 (2026-10-09), the product tree tag v2.0.0.157 carries
(PRs #116, #118, #119), ⛔ not walked by this release — the screens are the launch walk's; the build 2.0.0.166 block read at
origin/development 69d4b62 (2026-10-14) and the release's own cards, ⛔ not walked (RUN 11 walks them).