> For the complete documentation index, see [llms.txt](https://uliquid-1.gitbook.io/uliquid-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uliquid-1.gitbook.io/uliquid-docs/support/support-package.md).

# Collect a Support Package

What support or operators need for a fast investigation.

A good support package saves time and prevents misunderstandings. For every incident, collect specific information whenever possible.

## Minimum Information

* Workspace name or workspace ID.
* User email or user ID.
* Timestamp with timezone.
* Affected page.
* Action that was performed.
* Expected result.
* Actual result.
* Screenshot or screen recording.

## Trading Cases

Also include:

* Exchange.
* Exchange account label or ID.
* Symbol.
* Order type.
* Side.
* Size, price, and leverage.
* Order ID or client ID, if available.
* Position before and after the action.
* Screenshot from the exchange UI if live capital was involved.

## Bot and Grid Cases

Also include:

* Bot ID or grid instance ID.
* Template ID.
* Runner status.
* Last error text.
* Preview status and warning codes.
* Funding or BotVault ID.

## Wallet and Funding Cases

Also include:

* Wallet address.
* Network.
* Transaction hash.
* Asset and amount.
* Source and destination.
* Pending or confirmed status.
* Balance before and after the flow.

## Admin and Security Cases

Also include:

* User role.
* Expected permission.
* Audit entry, if available.
* Error message such as `403`, `429`, or `invalid_or_expired_code`.

{% hint style="info" %}
Never share API secrets, private keys, seed phrases, or OTP codes in a support package.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://uliquid-1.gitbook.io/uliquid-docs/support/support-package.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.