> For the complete documentation index, see [llms.txt](https://documentation.movatic.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.movatic.co/admin-site/debugging-common-issues-on-dashboard.md).

# Debugging Common Issues

This section will include steps to debug any common issues that may arise at some point after your system is setup. Behind the scenes, we work very diligently to keep our software optimized. With that being said, bugs will still occur and we understand how important it is to get these issues resolved as quickly and efficiently as possible.&#x20;

Before you reach out to Movatic for any bug issues:

* Make sure you're navigating directly to [admin.movatic.co](https://admin.movatic.co/) without any additional tags on the end (such as /#/login).&#x20;
* Try clearing your cache, doing a hard refresh, and logging out then logging back in.
* Try using an incognito browser.

In the event that you *do* have to contact us directly, there are some key elements to submitting a bug that will ensure that your report is top-notch and we are able to resolve the issue quickly:

1. Determine whether the bug is software related or not. All hardware issues are directed to the hardware manufacturer. Generally speaking, if an issue is occurring across multiple bikes, scooters, etc. then it's most likely a software bug. If you are unsure, reach out to us so we can make sure the issue is addressed regardless.
2. Take note if the issue is isolated or repeatable.
3. Describe how you got the bug to occur. What page were you on? What process were you doing?
4. Did you receive an error message? If so, what was included in the message?
5. Include any screenshots or video.
6. For smartphones, include the OS (iOS or Android) and device. For web pages, include the browser.
7. Send the information over by emailing to <support@movatic.co>.

{% hint style="info" %}
Movatic does not provide front line support to users (e.g. how to, refunds, assistance ending rentals, etc.). This support is done by the system operator while system operators forward all software bugs to Movatic.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.movatic.co/admin-site/debugging-common-issues-on-dashboard.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
