> For the complete documentation index, see [llms.txt](https://docs.ib.b2core.b2broker.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ib.b2core.b2broker.com/for-brokers/back-office-guide/processes.md).

# Processes

View the following information for each process:

**Date**

The date and time when a process started running.

***

**Process name**

The name of a process. Possible values:

* **Clear Cache** (`cache`) — clears cache for the specified time period.
* **Cancel Payments** (`cancel`) — reverts reward payments.
* **Create Payments** (`payments`) — initiates reward payments.
* **Process Payments** (`transactions`) — processes reward transfers.
* **Run Automation** (`schedule`) — runs consequentially the full process cycle (Sync Symbols + Sync Groups + Sync Trades + Create Payments + Process Payments + Sync Accounts).
* **Run Diagnostics** (`diagnostics`) — runs diagnostics of IB services.
* **Sync Accounts** (`accounts`) — runs synchronization of [accounts](/for-brokers/back-office-guide/platforms/accounts.md) with trading platforms.
* **Sync Groups** (`groups`) — runs synchronization of [groups](/for-brokers/back-office-guide/platforms/groups.md) with trading platforms.
* **Sync Symbols** (`symbols`) — runs synchronization of [symbols](/for-brokers/back-office-guide/platforms/symbols.md) with trading platforms.
* **Sync Trades** (`trades`) — runs synchronization of [trades](/for-brokers/back-office-guide/platforms/trades.md) with trading platforms.

***

**Memory**

The amount of memory used by a process.

***

**CPU Time**

The time which it took a process to run.

***

**PID**

The process identifier.

***

**Exit code**

The process result. Possible values:

* **0** — the process completed successfully.
* **1** — the process wasn't completed due to errors.
* **2** — the process was gracefully stopped due to service maintenance.


---

# 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://docs.ib.b2core.b2broker.com/for-brokers/back-office-guide/processes.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.