Integration Core help · for the operator (the Integration Manager) · graded against Core v1.0.0-rc.5 · written 2026-10-06 · re-read against rc.8's screens 2026-10-09 · where a newer Core words a screen differently, see the Glossary's "Changed in newer releases"
What this page restates, and from where: the setup guide, Steps 6 and 7, Getting alerts by email, The things you can press and What you must never do (screens re-derived 2026-09-27; card names 2026-10-02); the support runbook §2, §3, §3b and §4 (2026-09-13, re-looked-up 2026-10-02). Each section ends with its source line. Where this page and a paper disagree, report it; a section that read a newer build than its paper says so.
Your daily look at the Integrations Hub
Open Integrations Hub once a day. Read Connection Health first — every connection in one line — then the tiles and links in this order:
- Failed — fix the cause, then retry.
- Cannot tell if it arrived — leave it alone.
- Needs a decision — decide, then close it with a note.
- Reversals not confirmed (on the Day to Day card) — money owed; escalate if old.
- Money records waiting — the one number that says how many money records are in flight.
- Set aside (on the waiting card) — usually expired sign-in details.
Once a week: Waiting on a setup change, and Differences.
⭐ If something is genuinely stuck you will also be told in the bell. But one alert can stand for many records, so always count the rows on the tile or link, not the alerts.
Source: the setup guide, Step 7 (2026-09-27).
Read Connection Health first
Integrations Hub → Your connections → Connection Health. One line per connection: its state in words, since when, when it last looked for changes, and its counts of Failed, Money Records Waiting, Needs a Decision, Cannot Tell If It Arrived and Not Finished records.
⭐ First question on any problem: is the connection running at all? One dead connection produces dozens of stuck-looking records. If a connection is not green Live, start with the help page Troubleshooting for its word before you read any record.
The Connections with a problem tile counts the 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. ⚠ A connection switched on a moment ago counts until its first report, and one that has gone quiet is noticed at the next hourly check.
Source: the setup guide, Step 1 and Step 7 (2026-09-27); the support runbook §1 (2026-10-02).
Fix and retry a Failed record
Failed records do not resolve themselves. Open each one: "This record failed. Error: …".
- Read the error. Press Open … at the top to reach the iVendNext document it is about.
- Fix the cause — on the other system or in iVendNext.
- Press Retry.
⛔ Retry does not fix the cause. A failure that will fail again only fills the queue.
- A row that reads Cannot be sent ("The document this change belonged to no longer exists…"): nothing can send it. Fix it on the other system if it matters, then press Acknowledge so it stops being reported. It then reads Acknowledged and leaves the tile. ⚠ If there is no Acknowledge button, your role may not edit the record — ask an Integration Manager.
- A row that reads Failed and offers Acknowledge but no Retry: the connection marked it as a failure no retry can fix. Treat it the same way — fix it on the other system if it matters, then acknowledge it.
- Several at once: select them on Integration Activity and choose Actions › Retry selected. It tells you beforehand which it will skip and why, and afterwards which were sent, declined, failed, and not attempted at all. ⚠ Read the not attempted list — those still need a retry.
Source: the setup guide, Step 7 item 1 and The things you can press (2026-09-27); the support runbook §3; the Acknowledge button read at Core rc.5 (it is offered for both kinds of unfixable failure).
Leave Cannot tell if it arrived alone
A record on Cannot tell if it arrived (it reads Unverified on the list) says "Integration Core cannot tell whether this reached …".
⛔⛔ Do nothing to it. There is no Retry button and there must not be: sending it again could move the same money twice. It is not failed and not pending — we cannot tell. Only the other system can settle it, by the connection's next check or by a person there; the record's Error says which, where the connector wrote one.
If it is still there tomorrow, raise a ticket. Do not look for a way to force it.
Source: the setup guide, Step 7 item 2 (2026-09-27); the support runbook §2.
Answer a record that needs a decision
The record's banner is short labelled lines: Why: the connector's reason (its first line, in bold — Show technical detail opens the rest), Do this, Amount, Record, Who can open it, and "Not retried automatically: this record waits for a person to decide." If a Difference is open against it, it is named with a link. If other decisions are open on the same record it lists them ("Also open on the same record: … Answering this one does not close them.") — read them all first.
- Do what it asks, on the other system or in your books.
- Press Keep iVendNext Version. It asks for a note — what you decided and why — and will not close without one.
- The record then reads Decided.
⚠ A Decided record still shows Retry — read How Integration Core works, Why some records refuse a retry, before you press it.
⛔⛔ Keep iVendNext Version records your decision and does nothing else. It sends nothing and changes nothing in iVendNext. ⛔ There is no "use the other system's version" button: if that version is right, correct it on the other system and let the change come through again.
⚠ If no reason is written, raise a ticket rather than guessing — do not close it just to clear the tile. If the cause was fixed in iVendNext, a decided record may offer Re-check, which sends it back to the connection once more.
Source: the setup guide, Step 7 item 3 (2026-09-27); the support runbook §2, Needs Decision; the known issues §2, IC-MONEY-SHOWN-B1 (2026-10-02).
Check reversals that are not confirmed
Day to Day → Reversals not confirmed. iVendNext has reversed its side and the other system has not confirmed it. ⭐⭐ On a refund, the customer's money has not left yet. (A cancelled unpaid order or a reversed stock movement can wait here too.)
If one is more than a few hours old, raise a ticket. ⛔ Do not leave these. Retry is refused on them: sending again could reverse twice.
Source: the setup guide, Step 7 item 4 (2026-09-27); the support runbook §2, Reversal Pending.
Read the money records waiting
Money records waiting counts every money record that has not finished and that nobody has decided — one per change (the latest try). It is a count of records, ⛔ not a sum of money; a sale and its payment are separate records, so both count. Open it and the list says how many are coming in and how many going out.
It is not a to-do list by itself — most rows are also on another tile — but it is the one number that says how much is in flight.
- "No amount on this record" is ⛔ not zero: the connector did not record an amount of ours.
- Amount as Received is the other system's figure on arrival, where the connector passed it — shown, never compared.
Source: the setup guide, Step 1 and Step 7 item 5 (2026-09-27); the known issues §3 (2026-10-02).
Read why records are waiting
Look at the waiting card once a week (it is titled Waiting — clears by itself on rc.5; three of its five links do not clear by themselves).
- Waiting on a setup change — each row says Waiting on: … and, where the connector named the field, Open the fix (or Ask a … if you may not change it). One missing piece of setup often holds many records — fix it once and they all move. The row also says who re-checks it and how often.
- Set aside — "Set aside, not failed: it is picked up again by itself once the cause clears. Nothing is lost." Usually expired sign-in details: ask a System Manager to renew them. A connector may also set a record aside because the other system was down; then there is nothing to renew.
- Kept while switched off — drains by itself at about 500 records an hour once the connection is on. Nothing to fix — ⚠ unless the count stops falling: a full batch of records held behind unsettled ones can hide everything after them. That stall rings the bell; raise a ticket.
- Held behind an unknown attempt — ⛔ do not force it, and do not press the Retry button its record shows; only the other system can settle the earlier attempt.
- Waiting on Connected System — in progress with the other system. Nothing to do, though a list that only grows is worth a question.
Source: the setup guide, Step 1 and Step 7 (2026-09-27); the support runbook §2 and §8; the known issues §1, IC-R30
(2026-10-02).
Link a record by hand when no link exists
A record waiting because no link exists yet can be fixed from the screens: Record Links → Link manually. You need the connection, the record type, the other system's ID and the iVendNext record — and permission to change that iVendNext record as well (an Integration Manager alone is refused, by design).
⛔⛔ A link made by a person is never changed by syncing — if it is wrong it stays wrong. Check both IDs before you confirm. If you made a mistake, open the link and press Make inactive, then link it again.
Once the link exists, retry the waiting record — Link manually does not retry it for you.
Source: the setup guide, Step 7 and The things you can press (2026-09-27); the support runbook §8 item 1 and §10.
Work the Differences
Open each open difference. The title says which record and what differs; the message says it in plain words ("This connection reported different values for …: iVendNext has …, and … has ….").
- When you have dealt with it, press Mark resolved and say what you did.
- For three kinds — a record renamed in iVendNext, a link a sync moved, a hand-made link the sync would have changed — you may instead press Accept — don't report again unless it changes, with a reason. It is not reported again for 30 days while both values stay the same. ⛔ Not offered on a record that carries money.
- A Cancelled in iVendNext difference: a document the connection had already sent was cancelled here. Nothing was sent to the other system. Reverse it there by hand, then Mark resolved.
⛔ Neither button changes anything in either system.
Source: the setup guide, Step 7 (2026-09-27); the support runbook §3b; the known issues §2, IC-RELEASE-RC3-B1
(2026-10-02).
Switch a connection off and on
Connections → the connection → Switch off or Switch on (top right).
- Off stops sending and applying. Changes that arrive are kept and marked as waiting; nothing is lost.
- On re-queues the kept changes oldest first: one batch now, then 500 an hour. The message afterwards says how many were picked up.
- Your name and the time are recorded either way.
- A connection you switched off does not ring the bell about the records waiting for it. ⚠ Its money records still ring — a record nobody can tell arrived, an unconfirmed reversal, a decision, a failure. Answer them where the record offers a way, or switch it back on.
- To replace an ERP connection: switch the old one off, then set up and switch on the new one. Only one may run at a time; a switched-off one does not hold the place. Anything the old one created on the other system — keys, notifications, webhooks — is removed there by hand.
Source: the setup guide, Step 5, Step 7 and Removing a connection (2026-09-27).
Get the daily summary by email
Connections list → the ⋯ menu → Email me a daily summary. Once a day you get the Connection Health report by email, for the connections you are allowed to see. Stop my daily summary in the same menu ends it.
- Only the Integration Manager role sees these two menu items.
- Your user needs an email address, and the site needs an outgoing email account; if it has none, the screen says so.
- If you lose the right to read the Connections list, your summary is switched off within the hour.
Source: the setup guide, Getting alerts by email §2 (2026-09-27).
What every button does
| Button | Where | What it does | ⛔ What it does not do |
|---|---|---|---|
| Open … | a record about an iVendNext document | opens the document — how you reach the thing to fix | — |
| Open the fix · Ask a … | a Still needed item; a waiting record | opens the record that fixes it, at the field · assigns it to someone who holds the role that may change it | changes nothing itself |
| Retry | a failed record — and any other record the connection may still send, for someone who may edit it | sends it again; on a record that is not Failed the connector may decline | not offered where we cannot tell if the first send arrived, nor on a failure no retry can fix; does not fix the cause. ⛔ Do not press it on Held behind an unknown attempt; after retrying a Decided record, watch it yourself |
| Retry selected | Integration Activity, Actions menu | the same, for several; names what it skips and why, and what was not attempted | never touches the protected states |
| Keep iVendNext Version | a Needs a decision record | closes it with your note, name and time; it reads Decided | does not do what the record is waiting for; sends and changes nothing |
| Re-check | a decided record whose cause was fixed in iVendNext | sends it back to the connection once more | — |
| Acknowledge | a Cannot be sent record, or a Failed record marked as a failure no retry can fix | records you saw it and stops it being reported | recovers nothing |
| Mark resolved · Accept — don't report again unless it changes | a difference | records you dealt with it · for three non-money kinds, stops it being reported for 30 days while unchanged | changes nothing on either system |
| Link manually · Make inactive | Record Links | joins two records by hand · retires a link a person made | a hand-made link is never corrected by syncing; does not retry the waiting record |
| Switch on · Switch off | a connection | starts or stops sending and applying | loses nothing either way |
| Email me a daily summary · Stop my daily summary | the Connections list ⋯ menu | starts or stops your daily email | — |
Source: the setup guide, The things you can press (2026-09-27); the Retry and Acknowledge buttons read at Core rc.5; the known issues §2, IC-MONEY-SHOWN-B1 (2026-10-02).
Never edit these fields by hand
Do not edit the fields on these records — the state, the amounts, the references, the links, the sync positions. The system owns them and refuses the change, in its own words: "Some records are deliberately not retriable, and editing around that can send the same money twice or silence a failure that is still fixable."
On Record Links and Sync Positions the rows are read-only for you. ⛔ A sync position moved by hand skips every change between the two positions, silently.
⇒ Everything you are meant to do is a button. If the only way forward seems to be editing a field, raise a support ticket instead.
Source: the setup guide, What you must never do (2026-09-27); the support runbook §4.