> For the complete documentation index, see [llms.txt](https://help.helioscard.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.helioscard.xyz/help-and-troubleshooting/pending-transactions.md).

# Pending & processing transactions

Some actions in Helios — adding funds, withdrawals, receiving transfers, sell to repay — happen on a network and take a short time to settle. While that's happening, you'll see a **pending** or **processing** status.

## This is normal

A pending status means the action is in progress, not that something went wrong. The app updates the status automatically as it completes.

Common things that take a moment:

* **Adding funds (bridging in)** — see [Adding funds](/your-wallet/adding-funds.md)
* **Withdrawals** — see [Withdrawing funds](/your-wallet/withdrawing.md)
* **Incoming transfers you need to accept** — see [Sending & receiving](/your-wallet/send-and-receive.md)
* **Sell to repay** — see [Sell to repay](/credit-line-and-borrowing/sell-to-repay.md)

## What to do

1. **Wait.** Most actions finish within a few minutes.
2. **Don't retry repeatedly.** Starting the same action again while one is pending can be confusing — let the first one finish.
3. **Check for an action you need to take.** Incoming transfers may need to be accepted.
4. **Still stuck?** If something has been pending far longer than usual, [contact support](/help-and-troubleshooting/contact.md) with the details.

{% hint style="info" %}
Keep the app open or come back to it — the status refreshes on its own.
{% endhint %}

## When should I worry?

Most actions settle within a **few minutes**. If something has been pending **well beyond that** — and the app isn't showing a queue position or estimated wait — [contact support](/help-and-troubleshooting/contact.md) with the details and any reference ID.


---

# 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://help.helioscard.xyz/help-and-troubleshooting/pending-transactions.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.