Available for
- Roles: Administrator
- Plans: Starter, Premium, On demand, if the feature is enabled
The Integration History screen shows you the result of the exchanges between your systems and Mobility Work, without having to go through a support request.
The screen covers two types of exchanges: calls received by Mobility Work via the Partner API, and webhooks sent by Mobility Work to your systems.
Accessing the history
- Go to Network Settings from the Network menu.
- Open the Integration History tab.
- The list opens on the failures from the last 7 days — this is what you're most often looking for when arriving on this screen.
- Adjust the filters if needed.
Reading the list
Above the list, three counters summarize what you're looking at: the number of calls shown, the number of entries on this page, and the total number of entries over the period. Only the last one covers the whole period set by your filters; the first two only describe the current page.
Each row in the list corresponds to one call, not an isolated event. A single import can produce several entries — the batch received, its processing a few minutes later, then one entry per failed line. The screen groups them to present the call as a whole.
A row shows you:
- the integration concerned, for example Stock movements, Spare parts creation and update, or Webhooks;
- the address of the exchange: for a received call, the endpoint followed by the start of the request reference; for a sent webhook, the URL of your system and the status code obtained;
- the call's status as a tag: a failure reason, for example Spare part not found or Invalid data sent, or No error when the call succeeded;
- the number of entries attached to this call on the current page;
- the date of the call.
The first call in the list opens automatically, with its failure reasons already expanded, to show you what the detail contains without having to click.
Available filters
Four filters let you target what you're looking for.
Status
All (both), Failures (default value when the screen opens), Success.
Direction
All (default value), Received — calls your systems send to Mobility Work via the Partner API —, Sent — the webhooks Mobility Work sends to your systems.
Integration
Lets you target a specific integration: Stock movements, Spare parts information, Stock levels, Spare parts creation and update, Physical inventory, Location change, Storage locations, Equipment, Tasks, Activity reports, Webhooks.
The All integrations option shows them without distinction.
Period
Three windows are available: Last day, Last 7 days, Last 30 days. The screen opens on Last 7 days. Depending on your network's volume, the period actually available may be shorter: the oldest entries are regularly purged.
What the counters tell you
The screen's counters always speak in entries, never in business items. An entry is a line recorded by Mobility Work during processing, not a spare part or an equipment item.
Concretely, a call that imported 1,000 spare parts won't show "1,000 entries": nothing records the number of items contained in a batch. So you won't find a counter like "950 succeeded out of 1,000".
Behaviors to know
- Any filter change takes you back to page 1. Page 4 of a full list is not page 4 of a list filtered on webhooks, and an out-of-range page number would show an empty list that could be mistaken for no results.
- The list shows 20 entries per page, not adjustable. When a single call's entries don't all fit on one page, the screen tells you explicitly rather than letting its counter pass for a total. The message shown is: "This call has X entries on this page. More may be on the following pages — filter on 'Failures' to keep only what failed."
- When no exchange matches your filters, the screen shows "No integration activity for this period."
- If the history can't be loaded, the screen shows "The integration history could not be loaded. Please try again." Retry the operation before contacting support.
- If you expand a fully successful call, the detail shows "No errors recorded for this call."
- When the transmitted content can't be displayed, the screen shows "The sent data could not be displayed." In that case, communicate the request reference to support.
Sharing a filtered view
The filters and current page are embedded in the page's address. You can therefore copy the address from your browser's address bar and send it: the person who opens it gets exactly the same list, with the same filters.
This is especially useful in two situations: passing a failed import to a colleague in charge of fixing the data, or attaching the link to a support request, in addition to the request reference.
The recipient must be a network administrator to open the link — a user without that role will be redirected. The expanded detail of a call, however, is not part of the link: the recipient opens the filtered list, then expands the call on their own side.
Analyzing a failed call
- Find the call concerned in the list — failure reasons appear as tags on the row.
- Click the row to expand it.
- Review the failure reasons, then expand the one you're interested in to see the related entries.
The reasons, and why they're grouped
A call's detail groups entries by reason, not line by line. The reason is the useful unit: "3 spare parts not found" is a single thing to fix, whereas three separate lines would force you to piece the problem together yourself.
Reasons you may encounter:
- Batch received — Mobility Work has received your submission.
- Processed — the batch has been processed.
- Invalid data sent — the request's content cannot be used.
- Ambiguous reference — the reference provided matches several items.
- Spare part not found — no part matches the reference sent.
- Storage location not found — the location indicated doesn't exist in the network.
- Location change not possible — the part cannot be relocated.
- Creation ignored or Creation not possible — the item was not created.
- Processing not possible — an error occurred during processing.
- Webhook delivered or Webhook delivery failed — for sent calls.
- Integration event — an exchange the screen cannot yet name more precisely. Communicate the reference to support if you need it interpreted.
Success reasons are listed alongside failure reasons. Only failure reasons appear as tags on the collapsed row, up to two, with the rest counted.
The data sent
When the call includes a Batch received entry, a Show sent data button lets you view the content your system transmitted: references, quantities, unit prices, stock thresholds.
The sent data is always collapsed by default. It belongs to you, but it's bulky.
The case of sent webhooks
For every webhook sent by Mobility Work, the detail keeps the exchange with your system: the URL called, the status code of the response, and the response content returned by your system. The screen shows a Response line, followed by the code as a green or red dot, or the mention No response. The content sits behind a Show response button.
A status code shown as No response means your system didn't respond at all: domain name not found, server unreachable, connection refused. It is not a status code equal to zero. In that case, check that the configured URL is reachable from the outside.
The case of received calls
For a call received via the Partner API, the detail shows an Endpoint rather than a URL: the method and path called, with no domain name or parameters.
There's no response to view, and that's not an oversight. The Partner API acknowledges receipt immediately, then processes your submission in the background. The errors you care about most — a spare part not found, for example — are therefore recorded well after the response was already returned to you. Practical consequence: right after an import, the call may only show its Batch received entry. Come back a few minutes later to see the processing result and any errors.
Communicating a reference to support
A copy icon next to the reference lets you grab it in one click; each entry has the same icon for its own reference.
It's important to communicate this reference when contacting support: it allows the exchange concerned to be found immediately. When an entry shows Technical error, the message explicitly invites you to communicate the reference given to support — this is the case where the technical detail can't be presented as is, and the analysis has to be done by Mobility Work.
Entries spread across several pages
When a call has more entries than a page can display, the screen warns you and suggests filtering on Failures to keep only what failed. The number of entries shown for a call corresponds to what's on the current page, not necessarily the call's total.