Driveosplatform catalogue

When something is not working

When something is not working: what each message means, whom to contact and what can be fixed right away — without reading code.

When something is not working, guessing is the worst option. First recognise what is going on, then take the step from the table — and tell support what they need to solve it on the first try.

The company cannot take rides

CodeMeansFix
errors.launchNotReadyIt did not pass the readiness gate (12 checks)Home → Company readiness shows what is missing; the company owner fills it in
errors.moduleDisabledThe module is not enabled for the companyThe platform enables the module (Money → Modules); data stays
errors.tenantInactiveThe company is not active (trial, block)The platform checks the subscription and company status
400 uz key poljaAn invalid form field — key names the fieldThe field is marked with a message; fix it and save again

Sign-in and session

Code or symptomMeansFix
errors.invalidCredentialsWrong e-mail or passwordCheck case and spaces; use Forgot password?
errors.sessionExpiredThe session expired or was revokedSign in again; if it repeats, the platform checks account security
errors.accountInactiveThe account is deactivatedThe company owner reactivates it under Users
Sign-in asks for a code but you have no appTwo-factor protection is onUse a recovery code or ask the platform to reset the second factor

Rides

SymptomUsual causeFix
A ride waits but drivers “exist”Drivers are not on duty, lack valid documents, or their vehicle does not match the service typeFleet → Drivers and Alerts; assignment only offers eligible drivers
The ride cannot be cancelledIt is already finished or cancelled (errors.rideTransitionNotAllowed)Refresh the ride; if a new one is needed, create it
An offer does not reach the driverNotifications are off or the driver is pausedThe driver enables notifications and checks the shift state
The price in the app and in settlement differA different period, or the ride is not finished yetCheck the period and the ride status in Settlement

API and integrations

Status and codeMeansFix
401 errors.invalidApiKeyThe key is not recognisedCheck the X-API-Key header or Authorization: Bearer
403 errors.forbiddenThe key lacks a scopeThe company owner adds the scope (Company → Developer)
403 errors.apiKeyRevoked / apiKeyExpiredThe key was revoked or expiredIssue a new key and switch the integration
403 errors.apiKeyIpNotAllowedThe request comes from an address not on the listAdd the address to the key list or remove the restriction
429 errors.tooManyRequestsRate limit exceeded (120/min per key)Honour the Retry-After header; reduce calls or polling
A webhook does not arriveThe endpoint returns errors or the address was rejected (private address, http)GET /api/v1/webhooks shows delivery counts and dead letters

Apps on the phone

SymptomFix
No offers in the backgroundAllow notifications and background work; on Android disable battery optimisation for the app
Location is not being sentLocation permission must be “while using” or “always”; also check GPS is on
The map is blankNo network or the map key expired — ask the company to check map settings
The app asks for sign-in every timeThe session was revoked or “Remember me” is off
What to tell supportSend: the error code, the time (date and hour), the ride number (R-…) and the role you were using. Those four facts shorten a fix from a day to minutes.