Vibee

For owners and users

What to do when data does not save

Check whether your change was saved, understand the error code and test a button that does not work.

Check the result first

  1. Read the message

    The app may flag a required field, an unavailable slot, missing permission or a capacity limit. Correct the particular value according to the message.

  2. Check sign-in and connection

    Sign in again if your session expired. Check your connection if the internet is down. Note any unsaved information you need before refreshing the page.

  3. Check the data before trying again

    After a broken connection or e-mail error, check the overview and detail: the record may already exist. Repeating the action can create another booking or apply the change again.

Share the error code

The error message often includes Error code with a copy button. Give the owner the code, page address, approximate time and the action you performed. If no code is shown, describe the exact message and steps.

Do not send passwords, password setup links or unnecessary customer data. The owner can use the code with their assistant to find the cause.

An explanation for the owner

As the owner, open the app through its address in Vibee app management. A refused request may show an explanation below the error code, labelled Why (only you, the owner, see this). Ordinary app users do not receive this explanation.

If the message identifies an app setup error, give it to your assistant with the error code. Signing in repeatedly will not fix that setup error.

Open the app from Vibee management

Steps for the owner

Give your connected assistant the app and error code. Ask it to check the error record, capacity and permissions before changing settings. Error records have limited availability: up to 7 days and 500 entries per app.

Find the cause
In my app [name or address], [action] failed at about [time]. The error code is [code]. Find the cause in the error records and explain it. First check whether data was saved; do not repeat the action or change permissions without an explanation.

Check a button without saving changes

When saving app settings, the assistant also checks how buttons connect to their actions. This can catch some errors before the app reaches your team.

For a record action, bulk action or standalone button, ask for a test using a specific person’s access. It uses the live app’s settings. Stored data stays unchanged and no emails or other automated messages are sent. The test does not replace checking the whole form and its controls on a phone or computer.

A button does not work for a technician
In my Newman Repairs app, test the Record work button on the job detail page without saving changes. Use technician [email] and job [number or address]. Explain any refusal and do not change permissions yet.
How to check permissions

After the fix

Check the same workflow on a test record with the access of the person who had the error. If it persists, contact support and include the error code.

How to check limitsHow to set permissionsContact support