Troubleshooting and frequently asked questions (FAQ)

Here you will find common errors, known limitations and frequently asked questions about the ABAX integration, as well as who to contact for what.

TABLE OF CONTENTS

Responsibility: Telaris and ABAX
Common errors
Known limitations
What the module does not do
Frequently asked questions
Glossary

Responsibility: Telaris and ABAX

Telaris is responsible for the integration in Telaris – setup, import of trips and generation of order lines. The driving log itself, the GPS units and the data in ABAX rest with ABAX. If the question concerns GPS units, registration of trips or the ABAX account, contact ABAX.

NOTE: Telaris does not obtain and does not verify consent from drivers. The consent checkbox in Telaris is only a technical switch. The actual consent, and the responsibility for processing GPS and driving data, lies with the customer.

Common errors

Problem	Cause	Solution
`An error occurred during the OAuth process`	The authorisation code is invalid or expired, or the refresh token is missing	Re-authenticate via Administration → Integrations → ABAX → Authenticate.
`We couldn't authenticate with the integration. Please try re-authenticating`	Repeated failed authentication attempts	Check that the ABAX account is active and that OAuth access has not been revoked. Re-authenticate.
`An error occurred during the authentication process`	Neither OAuth nor Client Credentials is configured	Enter either OAuth connection or Client Credentials.
`Integration is missing required data`	Trip product or other required configuration is missing	Check that all required fields are filled in.
`An error occurred at Abax' end`	ABAX returned a server error	Wait and try again. If the error persists, contact ABAX.
`Insufficient permissions`	The access is missing the necessary scopes for the ABAX API	Verify that the ABAX account/client has scopes for trips, vehicles and people. Re-authenticate.
`You are looking up expenses for more than 150 trips`	The expense lookup exceeded the limit of 150 trips	Limit the period or the number of trips shown.
No trips are shown in the driving log tab	No drivers have consent activated, or there are no business trips	Check that at least one driver has consent, and that there are business trips (not private) in ABAX for the period.
Vehicle is not shown linked to a tag	The registration number does not match any tag, or several tags have the same name	Check that the tag exists with exactly the same registration number and the correct tag type. Link manually if needed.
Driver does not appear in the table	The driver has not driven a business trip yet, or import has not run	Wait for the next hourly run, or trigger import by opening the driving log tab.
The trip cannot be added	The trip is already completed or removed	Only trips with the status «new» can be added to orders.

Known limitations

Max 50 trips per import run (without pagination). Business-trip and consent filtering happens on these, so the number imported is often lower. With a large backlog, the import repeats automatically every hour.
ABAX has a limit of 60 API calls per minute. With many simultaneous users, this can cause temporary delays.
Expense lookup is limited to 150 trips per request.
GPS coordinates are not imported – only addresses are stored.
The integration only retrieves data from ABAX; nothing is sent back.
Drivers without a link to personnel do not get trips imported.
Telaris does not enforce the actual consent; it is the customer's responsibility.

What the module does not do

Does not send data to ABAX – communication is one-way.
Does not create trips or register drives – that is done by ABAX's GPS unit.
Does not handle private trips – only business trips are imported.
Does not calculate the mileage allowance rate – the price is controlled by the trip product.
Does not support real-time tracking of vehicles.
Does not obtain consent from drivers.

Frequently asked questions

Do all drivers have to give consent?

No, only drivers whose trips are to be imported. Drivers without consent are ignored entirely at import.

Where is consent set – in ABAX or in Telaris?

The checkbox is set in Telaris (Administration → Integrations → ABAX → the driver table). The actual consent must be obtained from the driver by the customer beforehand.

What happens if a driver is not linked to personnel?

Trips for drivers without a link are not imported. The link can be set manually, or automatically if the email matches a person in Telaris.

Can I use Client Credentials instead of OAuth?

Yes, if the customer has created their own API client at ABAX. Then no user login is required. Enter the ID and secret in the setup.

What is the difference between test and production environment?

The test environment uses ABAX's sandbox with test data. The production environment retrieves real data from the customer's ABAX account. Switch to prod when the setup is verified.

How often are trips imported?

Automatically every hour, and manually every time the driving log tab is opened (with a one-minute cooldown).

Can a trip be added to several orders?

Yes, as long as the trip has the status «new». Trips already added to the current order are marked «Already added to the order».

What happens to trips that are removed?

They get the status «removed» and disappear from the list, but are not deleted from the database.

Why do I not see the driving log tab?

The tab is only shown when at least one driving log integration is activated. Check that ABAX is activated under Administration → Integrations.

Why did not all trips come in at once?

Each run retrieves a maximum of 50 trips, and filtering happens on these. With many trips it takes several runs. The import runs every hour.

What about private trips?

They are not imported at all – skipped at retrieval and never stored in Telaris.

Glossary

Term	Explanation
ABAX	External service for driving log and GPS tracking of vehicles.
Driving log	A collection of registered trips in ABAX.
Business trip	A trip categorised as a business trip in ABAX. Only this type is imported.
Consent	A technical checkbox per driver in Telaris. Must be activated for trips to be imported. The actual consent is obtained by the customer.
Add to the order	A button in the driving log tab that creates order lines for mileage and expenses.
Mark completed	A button that sets the trip's status to completed and removes it from the list.
Remove	A button that sets the trip's status to removed. Shown only for trips that are not added to an order.
OAuth	An authentication method where the user logs in via ABAX and grants Telaris access.
Client Credentials	Alternative authentication with API keys, without user login.
Cooldown period	Automatic waiting time between import runs to avoid overload.

Recent Searches

Troubleshooting and frequently asked questions (FAQ)