Integration Activity
Integration Core · checked 2026-10-15
Integration Activity lists every change that crosses between iVendNext and a connected system, one row per try: its state, its amount where it carries money, the record it is about, and what went wrong.
The Integration Activity list
Open it from the Hub's Day to Day card, or from a tile. Try No. counts the tries of a change and Latest Try marks its newest row. Each row's chip shows the record's state in the Hub's words (see What each state means).
- Retry selected (in Actions, after ticking rows) retries several records at once. It says before and after what it did: skipped records are in a state that refuses a retry, each with its reason; records the connection declined are not sent again (orange) — correct, not a fault; not attempted ones still need a retry; and where the retry stopped with an error, whether anything was sent cannot be told — open the record before retrying again. Judge each outcome from the record's own state.
- Erase personal data and Erase personal data even if unfinished, for a System Manager: see Personal data.
- Opened from Money records waiting, the list says how many are coming in and going out.
The record
The first part of the form says what the record is about. Every field on this form is set by the system.
| Field | What it is |
|---|---|
| Connection | the connection this record belongs to |
| Direction | Inbound (into iVendNext from the other system) or Outbound (from iVendNext to the other system) |
| Record Type | the kind of record, as the connection declared it |
| Operation | what is being done: Create, Update, Delete, Cancel, Refund and others. A retry repeats the same operation |
| Incoming Record | for an inbound record, the arrival it came from (Incoming Records) |
| Reference Record Type · Reference | the record in iVendNext this is about |
| ID in Connected System | see below |
| Try No. · Latest Try | which try this is, and whether it is the newest |
ID in Connected System
The other system's number for the record — empty until it answers. You see it on a record, an incoming record, a difference and a record link.
Outcome
What happened to the record.
| Field | What it is |
|---|---|
| Status | the record's state; the chip and the banner say it in the Hub's words (What each state means) |
| Delivery Outcome | see below |
| Waiting On (or Earlier Hold) · Cause of the Wait | see below |
| Failure Kind | see below |
| Started At · Completed At | when the record was opened and closed |
| Waited Before It Ran | ticked when the record waited before it ran |
Delivery Outcome
On a record that was sent:
- Landed — it arrived on the other system, even if the other system refused it. Read the record's Error.
- Never Sent — it never left.
- Unknown — we cannot tell.
On a record whose error (or reason) says nothing was sent, Landed means the connection decided to write nothing there, on purpose.
Waiting On, Earlier Hold and Cause of the Wait
- Waiting On — on a waiting record, why it waits, in the connector's words. The same field reads Earlier Hold once the record stops waiting, and shows what it last waited on. The Report view's column reads Hold Reason.
- Cause of the Wait — the same reason as a short key, where the connector passes one; the same on every record waiting on that thing. Waiting, by cause on the Hub counts records by it.
Failure Kind
Set by the system, on some records, to say why a retry cannot help or why the record waits:
- Lost Outbound — the iVendNext document is gone, so the change can never be sent.
- Retry Cannot Fix — the connection says the other system will refuse it every time.
- Switched Off — a Waiting record kept while its connection was off, or held behind an unknown attempt.
Blank on an ordinary failure: Retry can help once the cause is fixed. For the first two, see Cannot be sent. Call support if a record you know can be sent reads Retry Cannot Fix.
As the other system sent it
Content from Connected System: what the other system sent for a record that was already completed, so you can compare it with the iVendNext record. Only an Integration Manager or a System Manager can read it.
Amount
On a record that carries money, and who acted on the record.
| Field | What it is |
|---|---|
| Money Record | ticked when the record type carries money, as the connection declared it |
| Amount · Currency | the amount in iVendNext, checked against the other system's |
| Claimed Amount · Claimed Currency | the amount the other system reported back for what crossed |
| Final Bill in Connected System · Final Bill Currency | see below |
| Amount as Received · Currency as Received | see below |
| Amount Confirmed | see below |
| Test Record | made by a certification run, never counted as real activity |
| A Newer One Arrived | on a record that was not imported: a newer delivery has arrived |
| Retry Requested By | who pressed Retry |
| Decided By · Decided On · Decision Note | who decided what to do with a record that needed a person, when, and their note |
A figure is shown with a currency symbol only where its own currency is known. No amount on this record is not zero: the connector did not record an amount of ours. Under the amount, the banner says whether the other system agreed: Reported by …: …, not … when it reported a different figure; This amount has not been confirmed by … while nothing has come back; This amount was never confirmed by … on a failed record. An unconfirmed amount is not a wrong one — check the figure on the other system before acting on it.
Amount as Received and Final Bill
- Amount as Received · Currency as Received — the other system's figure when it arrived, where the connector passed it.
- Final Bill in Connected System · Final Bill Currency — the other system's final bill, where the connector reports it.
Both are shown, never compared. Blank means not reported, never no difference.
Amount Confirmed
Ticked when the amount the other system reported back for what crossed matched ours. It is not their final bill: a system that adds its own tax or fee can bill more while the tick stands. Check the bill on the other system itself.
Technical details
Folded away, for support: Error (the most recent reason; cleared 30 days after the record is done or has failed), Summary Status, Duplicate Check ID, Source Log Entry, Batch Reference, Queue Reference in Connected System, Locked At and Lock Expired, and — for an Integration Manager or a System Manager — who erased personal data and when, and Request Data and Response Data: what was sent and what came back, with only the agreed fields kept.
Summary Status
A three-word summary: Unprocessed, Failed or Processed. Never reason from it on a money question. It reads Failed on an Unverified record too, where nobody presses anything, and Unprocessed on a waiting record a person must fix. Read the record's own state and banner instead.
What each state means
The chip on the list and the banner on the form use these words. The stored Status is in brackets where it differs. A record kept while switched off, or held behind an unknown attempt, reads Waiting on the chip; its banner says which.
In progress
(Queued, Pending, Retrying, Accepted.) On its way: queued, being sent, being retried, or accepted by the other system and not yet final. Nothing to do. If the other system accepted it but it is still not final after four hours, the bell says so — that is a money question for support.
Waiting
(Blocked.) The record waits on something it does not have yet, and is not failing. Its banner says Waiting on: and why.
- Read Waiting on:.
- Where the record offers Open the fix, fix that one thing — it often frees many records at once. Where it shows Ask a …, ask that person; the button assigns the record to them.
- Waiting for a record link? Use Link manually on Record Links, then retry the record.
Otherwise nothing here clears it, and Retry will not move it: ask whoever supports that connection. The bell rings once a record has waited longer than the connection's Alert If Waiting Over (minutes). If the other system no longer needs the record — the order was cancelled there before it was imported — closing it is the connection's job. Do not create an item just to make it go through.
Kept while switched off
(Blocked, Failure Kind Switched Off.) The record arrived or was made while its connection was switched off. It is kept, and nothing is lost. Once the connection is switched on, kept records are picked up oldest first: one batch at once, then about 500 an hour. If the connection is still off, nothing moves: switch it on (Connections).
Held behind an unknown attempt
(Blocked, Failure Kind Switched Off.) An earlier attempt at the same record may already have reached the other system, so sending this one could duplicate it. Do nothing: do not force it, and do not press the Retry button the record shows. It moves once the other system settles the earlier attempt. Call support if it is still held after a day.
Set aside
(Deferred.) Set aside, not failed. It is picked up again by itself once the cause clears, and nothing is lost. Usually the other system refused the sign-in details; a connector may also set a record aside while the other system is down. If the connection reads Sign-in refused, ask a System Manager to renew the details. Otherwise wait. After 12 hours the bell says so.
Reversal not confirmed
(Reversal Pending.) iVendNext reversed its side and the other system has not confirmed its side. Whether it went through there is not known yet — it may have. Do not reverse it by hand on the other system and do not refund the customer by hand: either could reverse twice. Retry is refused for the same reason. The connection's next status check settles it. After four hours the bell rings; call support if one is more than a few hours old.
Failed
Tried, rejected, and parked for a person. It does not fix itself.
- Read the error in the banner. Show technical detail opens the rest.
- Fix the cause, here or on the other system. The record's Reference opens the iVendNext document.
- On a money record going out, check the other system first: Retry asks whether to send it again, because Integration Core cannot tell whether the earlier send arrived. If the document is already there, do not retry — call support. Otherwise press Retry. It does not fix the cause.
The document was cancelled or deleted before it was sent? Press Retry; the connection closes the record when nothing is owed. If it is still Failed and now offers Acknowledge, see Cannot be sent.
Cannot be sent
The iVendNext document this change belonged to no longer exists (Lost Outbound), so the other system can never be told. No retry can help. A Failed record that offers Acknowledge but no Retry is the same: the connection marked it as a failure no retry can fix (Retry Cannot Fix).
- If it matters, fix it on the other system by hand.
- Press Acknowledge. It records that you saw it and stops the alert; it recovers nothing. The record then reads Acknowledged.
Unverified
We cannot tell whether it reached the other system. It may have landed. It is not failed and not pending. The Hub counts it under Cannot tell if it arrived.
Do nothing. Never retry it and never try to force it — sending again could move the same money twice. Only the other system can settle it: the connection's next status check, or a person there. A burst right after go-live usually settles on the next check. Call support if it is still there tomorrow.
Needs a decision
(Needs Decision.) A person must decide what happens to this record. It is never retried automatically. The banner says Why:, Do this:, the amount and the record; if other decisions are open on the same record, it lists them (Also open on the same record: …) — read them all first.
- Do what it asks, on the other system or in your books.
- Press Keep iVendNext Version, write a note — what you decided and why — and press Close with a note. The record reads Decided.
Keep iVendNext Version records your decision; it sends and changes nothing. If the other system's version is right, correct it there first and say so in the note. Do not close it just to clear the tile.
Decided or Ignored
(Ignored.) Closed on purpose, not failed. Decided: a person closed it with Keep iVendNext Version — their name, the time and their note are on it. Ignored: the connection closed it, for example because that record type is switched off. Nothing to do.
If the cause was fixed in iVendNext, a decided record offers Re-check, which sends it through the connection once more. A decided record also shows Retry; if you press it, follow the record on Integration Activity yourself until it finishes — neither the bell nor Money records waiting will.
Applied
Done: the change landed.
Cancelled
Reversed on both sides.
Superseded
A later change replaced this one. Running it again would put the old version back.
Skipped
(Not Applicable.) Nothing was owed for this record. The form shows Reason instead of Error.
Test record
Made by a certification run, not customer work. Never counted on the Hub, and never retried.
The buttons on a record
Only someone who may edit the record — an Integration Manager or a System Manager — sees Retry, Re-check, Acknowledge and Keep iVendNext Version. Anyone else: ask one.
| Button | What it does |
|---|---|
| Retry | sends the record through its connection again (an inbound one is applied again). It does not fix the cause |
| Re-check | on a decided record, sends it through the connection once more |
| Acknowledge | on a record that cannot be sent, records that you saw it and stops its alert |
| Keep iVendNext Version | closes a record that needs a decision, with your note |
| Open … | on a record that needs a decision, or an inbound record, opens the iVendNext document it made or is about |
| Open the fix · Ask a … | on a waiting record, opens the field that clears the wait, or asks the person who can change it |
When Retry is not offered
There is no Retry when any of these applies:
- the state refuses a retry — In progress while it is being sent or was accepted (Pending, Accepted), Unverified and Reversal not confirmed, because the first send may already have arrived; Needs a decision, because a person decides first; Applied, Cancelled, Superseded and Skipped, because the change already landed. There is no override, for anyone;
- it cannot be sent, or the connection marked it as a failure no retry can fix;
- it is a test record;
- its connection is switched off;
- its connector offers no retry;
- you may not edit it.
Some records show Retry that should not be pressed: never press it on Held behind an unknown attempt, and after retrying a Decided record, follow it until it finishes.