Troubleshooting

I cannot sign in

• Check that you are on app.manisma.com and not on api.manisma.com.
• Check your email address and password; ask an Admin to check your account status.
• A technician needs both a user account and a link to a technician record.
• A cancelled or suspended subscription can block the app, even when the login is correct.

The Admin menu is missing

Admin only appears for the Admin app role. Planner, Office, and Technician do not see this menu. The Admin app role is not the same as the built-in Directus Administrator.

An address has no route or travel time

Check street, house number, postal code, city, and country. Save the address again or use Admin → Import / Export → Localize addresses. A map quota can temporarily stop bulk processing.

A job cannot be scheduled properly

Check the service address, estimated duration, required skills, number of technicians, work hours, breaks, and date exceptions. A warning does not always block manual scheduling, but AI respects hard availability constraints.

The client does not receive email

1. Check that email is enabled.
2. Check the SMTP host, port, username, sender, and secure setting.
3. Save a new password again when it may have been changed; the existing password is never shown again.
4. Send a test email and check spam.
5. Check that the client or contact person has a valid email address.

Photo or signature is missing

Wait until the upload is finished before you confirm the form. Check the network connection and file size. With a required artifact, the form must report what is missing. Report repeated loss to the administrator so that storage and backups can be checked.

I see old data

Tap the refresh button (circling arrows) in the header. On My schedule and on a job you can also pull down to refresh. If you come from an area without coverage, go back online so the app fetches the latest data. Data shown offline is at most 24 hours old and carries an orange offline bar.

My offline changes are not synchronized

1. Check your connection; synchronizing happens automatically as soon as you are online again or sign in again.
2. View the bar with the number of pending changes and choose Sync now.
3. Changes that cannot be processed remain in the bar; view them there and delete them if needed.
4. Do not sign out unnecessarily while changes are pending. They stay saved, but preferably synchronize first when there is a connection.

The app does not show a new version

Close the app completely and reopen it. A new version installs itself after the app is fully closed and reopened.

API returns 401 or 403

• 401: header or key missing, key is wrong, or has been deactivated.
• 403: add the write scope for POST/PATCH. The current API allows GET with any valid active key; still use read as a clear administrative label.
• The raw key cannot be read back; if in doubt, create a new one.

API returns 404 for an existing id

The API also returns 404 when the record belongs to another tenant. Check that you are using the key from the correct organization and that the id comes from an earlier response of that same key.

Webhook test fails

Check HTTPS, a valid public certificate, port 443/8443, DNS, and a fast 2xx response. Redirects and private addresses are rejected. Verify the signature over the raw body. Check the delivery log for HTTP status and last error.

Billing blocks access

An Admin opens Admin → Billing. Complete an outstanding payment, update the payment method, or reactivate a cancelled subscription. Cancellation is immediate. Make a full data export before the end of a retention period when data must be preserved.