Read the sync status screen and fix failuresUpdated
See what has been sent to your ERP, what is waiting or refused, and how to fix and resend readings, work requests and usage. Includes the alerts Vectis sends.
Each ERP connection has a status screen that shows whether readings are getting through, and a delivery history that lists everything sent: meter readings, and, where the connection sends them, work requests and monthly usage. Anyone with the View ERP connections permission can look. Resending and dismissing need Manage ERP connections.
The status screen
Open Settings → Integrations → ERP connections, open a connection and stay on the Overview tab. The Status card shows:
- The connection's status and how long it has been in it.
- Last successful delivery and Next scheduled run.
- Counts for Waiting, Delivered (7 days), Failed (7 days), Rejected (7 days), Held for review and Unmapped vehicles. Select a count to jump to the matching items, or for unmapped vehicles to the Asset mapping tab.
- Last problem, in plain language. Select Details to see the ERP's own message.
- People have been alerted when an alert is open.
The screen refreshes itself every minute.
Connection statuses
| Status | What it means | What to do |
|---|---|---|
| Draft | Set up but not started. Nothing is sent. | Finish set-up, then Activate. |
| Active | Sending on schedule. | Nothing. |
| Paused | You paused it. | Resume when ready. |
| Degraded | Your ERP has been failing or unreachable for longer than the alert threshold (6 hours unless you change it). Items are kept and retried. | Check your ERP. See below. |
| Needs attention: credentials | Your ERP refused the credential. The connection pauses at once and nothing more is sent. | Replace the credential on the Credential tab. Sending resumes. |
| Mapping needs review | The field mapping needs fixing before sending can carry on. | Open Field mapping and fix the problems shown. |
| Disabled | The ERP add-on is switched off for your organisation. | Contact Vectis. |
The delivery history
Open the Delivery history tab to see every item, newest first, with its vehicle, asset number, what it is and when. Use the filters All, Waiting, Delivered, Rejected, Failed and Held for review.
Each item says what it is:
| Label | What was sent |
|---|---|
| Odometer with kilometres | An odometer reading. |
| Engine hours with hours | An engine hours reading. |
| Work request | A service request raised from a failed inspection, sent as a work request. See Send failed inspections to your ERP as work requests. |
| Usage with kilometres | One vehicle's usage for a month and cost centre. See Send monthly usage to your ERP. |
Once your ERP accepts an item, its reference is shown under it: ERP reference for readings and usage, Work request and the number for work requests.
A month's usage that changed after it was sent appears again as a new usage item. Your ERP is told it is a correction, so it replaces the first one rather than adding to it.
Item statuses
| Status | Meaning |
|---|---|
| Waiting | Queued, or being retried after a temporary problem. The next attempt time is shown. |
| Delivered | Your ERP accepted it. Each item is delivered once, in order for each vehicle. |
| Rejected | Your ERP refused it and gave a reason, or Vectis could not send it. The reason is shown in plain language. It is not retried. |
| Failed: not delivered | Your ERP could not be reached for 72 hours, so Vectis stopped trying. |
| Held for review | The reading is lower than the last one sent, so it was not sent. |
| Replaced by a newer reading | A newer reading for the same vehicle and meter took its place before it was delivered. |
| Dismissed | You chose not to send it. |
Fix a failure
Temporary problems
When your ERP is down or slow, Vectis keeps the items and retries with longer and longer gaps for up to 72 hours. When the ERP recovers, the queue drains without sending anything twice. After 72 hours the items become Failed: not delivered. Once your ERP is healthy, open Delivery history, filter by Failed and select Resend on each one.
A rejected item
Read the reason
On Delivery history, filter by Rejected. The red text under the item says why, for example that the asset number is unknown. Select Details for your ERP's exact message.
Fix the cause
Usually this is the asset number (see Map vehicles to ERP asset numbers) or a field in the Field mapping.
Resend
Select Resend on the item. It is queued again using your current mapping and asset number.
A work request or usage item for a vehicle with no asset number in this connection is not sent. It shows as Rejected with "Not sent: … isn't mapped to an asset … Map it, then resend." Map the vehicle, then select Resend.
A reading held for review
A reading lower than the last one sent is held, usually because of a mistake. If it is wrong, select Dismiss. If it is right, for example because the odometer was replaced, select Send as replacement. Your ERP is told it is a replacement reading, not a normal one.
A refused credential
On Needs attention: credentials, replace the credential on the Credential tab. The connection resumes and the waiting items are sent. Items held while the credential was refused are kept for 30 days.
Alerts
People with the Manage ERP connections permission are alerted by email and in the app when:
- a credential is refused, straight away;
- a connection has been Degraded for longer than the alert threshold;
- items have expired as Failed: not delivered.
You get one alert per problem, not a stream, and a recovery email when the connection is healthy again.
Change when the degraded alert is sent
The threshold is 6 hours by default. To change it, open the connection's Settings tab, set Alert after (hours of failures) to a number from 1 to 72, and select Save. You need the Manage ERP connections permission. The setting is per connection.
Daily digest
A daily digest goes out at 07:00 local time listing unmapped vehicles and rejected readings. It is only sent on days when there is something to report.