> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vecbase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get help

> Try a few quick checks, then send the Vecbase team the information needed to help you.

When something does not work as expected, a few simple checks often solve it.
If they do not, contact the Vecbase team from your workspace.

## Quick checks

Before opening a request:

1. refresh the page once;
2. confirm you are in the intended [workspace](/workspace/overview);
3. check that the Agent or [Scheduled Task](/agents/scheduling) is active;
4. confirm the Agent still has access to the needed
   [file space](/agents/files) or [Connection](/workspace/connectors);
5. review [**Usage** or **Billing**](/workspace/billing) for a paused balance or
   plan limit;
6. try a smaller version of the same task.

Do not repeatedly submit an action that creates, sends, or deletes something.
Check whether the first attempt already finished.

## Open a support request

Open **Support** in the workspace and create a new request. Choose a short
title that describes the visible problem, such as “Weekly task stopped
running” or “File preview stays blank.”

Keep one issue in each request. This makes updates easier to follow.

## What to include

Tell the support team:

* what you were trying to do;
* what you expected to happen;
* what happened instead;
* the approximate time and your timezone;
* the workspace, Agent, or task name;
* the exact error text, if one appeared;
* a screenshot with private information hidden.

Simple steps such as “open Agent, choose Scheduled Tasks, select Weekly Update”
are especially helpful.

## What not to send

<Warning>
  **Never send secrets**

  Do not include passwords, one-time codes, secret keys, access tokens, or full
  private documents. The support team does not need them to investigate.
</Warning>

## Follow the reply

Return to **Support** to read replies and add information. If the issue changes
or a new issue appears, open a separate request instead of mixing unrelated
problems.

When the issue is resolved, keep the final explanation if it will help your
team next time.