---
title: "Sweeping blocks to improve dashboard performance"
slug: "block-sweeping"
updated: 2025-07-22T11:08:21Z
published: 2025-07-22T11:08:21Z
canonical: "support.lusid.com/block-sweeping"
---

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

# Sweeping blocks to improve dashboard performance

By default, the Order Blotter displays active [blocks](/v1/docs/what-is-order-blocking-in-lusid), that is, blocks with any orders or placements that are *not* closed or cancelled.

LUSID allows you to mark inactive blocks as swept to improve the performance of the Order Blotter. [Read more on using the Order Blotter.](/v1/docs/using-the-order-blotter) ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image(923).png?sv=2026-02-06&spr=https&st=2026-11-09T06%3A14%3A15Z&se=2026-11-09T07%3A14%3A15Z&sr=c&sp=r&sig=NJeWF%2BPDYFOxPklphr%2BCK3frb%2F9ujSV3lmlAJzkWXAI%3D)

## How do I sweep a block?

For LUSID to successfully sweep a block, the block must meet the following requirements:

- All [orders](/v1/docs/what-is-an-order-in-lusid) are in one of the following states:
  - Closed
  - Cancelled
  - Booked
- All [placements](/v1/docs/what-is-a-placement-in-lusid) are in one of the following states:
  - Allocated
  - Over-allocated
- All [allocations](/v1/docs/what-is-an-allocation-in-lusid) are in one of the following states:
  - Closed
  - Cancelled
  - Booked
- [Executions](/v1/docs/what-is-an-execution-in-lusid) and allocations have *not* been modified since the specified `LatestAllowableModificationTime`.

LUSID evaluates whether the states of the block and its related entities meet the requirements above, and if so, allows you to update the block state to `Swept`.

To update a block state to `Swept` (providing the block meets all of the conditions above):

LUSID APILuminesce

Call the [SweepBlocks](https://www.lusid.com/docs/api/lusid/endpoints/order-management/SweepBlocks) API, for example:

```json
curl -X POST 'https://<your-domain>.lusid.com/api/api/ordermanagement/SweepBlocks'
  -H 'Content-Type: application/json-patch+json'
  -H 'Authorization: Bearer <your-API-access-token>'
  -d '{
  "blockIds": {
    "ORDER-C-BLK": {
      "scope": "Finbourne-Examples",
      "code": "ORDER-C-BLK"
    },
    "ORDER-1-BLK": {
      "scope": "Finbourne-Examples",
      "code": "ORDER-1-BLK"
    },
    "ORDER-B-BLK": {
      "scope": "Finbourne-Examples",
      "code": "ORDER-B-BLK"
    }
  },
  "latestAllowableModificationTime": "2025-07-21NLDN_Close"
}'
```

Alternatively, write a Luminesce SQL query using the [Lusid.Block.Writer](/v1/docs/lusidblockwriter) provider to set the block `isSwept` value to `True`, and execute it using a tool such as the LUSID web app. [See an example.](/v1/docs/lusidblockwriter#example-4-mark-blocks-as-swept)

![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image(922).png?sv=2026-02-06&spr=https&st=2026-11-09T06%3A14%3A15Z&se=2026-11-09T07%3A14%3A15Z&sr=c&sp=r&sig=NJeWF%2BPDYFOxPklphr%2BCK3frb%2F9ujSV3lmlAJzkWXAI%3D)

Note the following:

- Once you sweep a block, LUSID no longer includes the block in evaluations of the current state of orders.
- You can view historical blocks (that is, blocks closed or cancelled on previous days) by selecting a date range.