> For the complete documentation index, see [llms.txt](https://docs.hub88.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hub88.io/product-news/may-2025/introducing-flagged-activity.md).

# Introducing Flagged Activity

**Released**: **28 May 2025**

***

You can now easily spot and follow up on unusual or problematic transactions using the new[ Flagged Activity](/operator-backoffice/transactions-management/flagged-activity.md) view. We’ve built this to save your team's time and help you focus on what matters — whether it’s resolving stuck rounds or reviewing big wins. Here’s what’s included:

* System-flagged transactions, based on:
  * Failed transactions (declined with `RS_ERROR_UNKNOWN`)
  * Big wins (over €40,000 and 350x+ bet-to-win ratio)

From here, you as an operator can:

* Review only flagged transactions without going through all activity.
* Track investigation progress with statuses: `FLAGGED`, `INVESTIGATING`, `RESOLVED`.
* Create support cases directly from flagged entries, which will become prefilled and ready in HubConnect for finalizing.
* Collaborate as a team — investigation status updates are visible to all users in the same account.

Flags stay visible for 30 days, or disappear if the issue is resolved (e.g. transaction retry succeeds). Whether you're handling support, fraud checks or compliance reviews, this should take some pressure off your daily operations.

<figure><img src="/files/vQsxKCOvZI23nFFiNVe5" alt=""><figcaption><p>Flagged Activity view</p></figcaption></figure>


---

# 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.hub88.io/product-news/may-2025/introducing-flagged-activity.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.