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

# Prioritized Sync with Sync Rules

> Assign sync priorities to bucket definitions in legacy Sync Rules so that important data syncs before the rest.

<Info>
  Sync Rules are deprecated. For the Sync Streams version of this page, see [Prioritized Sync](/sync/streams/prioritized-sync).
</Info>

## Overview

PowerSync supports defining sync priorities, which allows you to control the sync order for different data. This is useful when certain data should be available sooner than others.

In Sync Rules, you assign priorities to bucket definitions. The priority determines when data in that bucket syncs relative to other buckets.

<Note>
  **Availability**

  This feature was introduced in version **1.7.1** of the PowerSync Service, and in the following SDK versions:

  * [Flutter v1.12.0](/client-sdks/reference/flutter)
  * [React Native v1.18.1](/client-sdks/reference/react-native-and-expo)
  * [JavaScript Web v1.14.2](/client-sdks/reference/javascript-web)
  * [Kotlin v1.0.0-BETA26](/client-sdks/reference/kotlin)
  * [Swift v1.0.0-Beta.8](/client-sdks/reference/swift)
  * [.NET v0.0.6-alpha.1](/client-sdks/reference/dotnet)
</Note>

## Why Use Sync Priorities?

PowerSync's standard sync protocol ensures that:

* The local data view is only updated when a fully consistent checkpoint is available.
* All pending local changes must be uploaded, acknowledged, and synced back before new data is applied.

While this guarantees consistency, it can lead to delays, especially for large datasets or continuous client-side updates. Sync priorities provide a way to speed up syncing of high-priority data while still maintaining overall integrity.

## How It Works

Each bucket is assigned a priority value between 0 and 3, where:

* 0 is the highest priority and has special behavior (detailed below).
* 3 is the default and lowest priority.
* Lower numbers indicate higher priority.

Higher-priority data syncs first, and lower-priority data syncs later. If you only use a single priority, there is no difference between priorities 1-3. The difference only comes in when you use multiple different priorities.

## Syntax and Configuration

Define priorities using the `priority` YAML key on a bucket definition, or with the `_priority` attribute inside a parameter query:

```yaml theme={null}
bucket_definitions:
  # Using the `priority` YAML key
  user_data:
    priority: 1
    parameters: SELECT request.user_id() AS id WHERE ...
    data:
      # ...

  # Using the `_priority` attribute (useful for multiple parameter queries with different priorities)
  project_data:
    parameters: SELECT id AS project_id, 2 AS _priority FROM projects WHERE ...
    data:
      # ...
```

<Note>
  Priorities must be static and cannot depend on row values within a parameter query.
</Note>

## Example: Syncing Lists Before Todos

Consider a scenario where you want to display lists immediately while loading todos in the background. This approach allows users to view and interact with lists right away without waiting for todos to sync.

```yaml theme={null}
bucket_definitions:
  user_lists:
    priority: 1  # Syncs first
    parameters: SELECT id AS list_id FROM lists WHERE user_id = request.user_id()
    data:
      - SELECT * FROM lists WHERE id = bucket.list_id

  user_todos:
    priority: 2  # Syncs after lists
    parameters: SELECT id AS list_id FROM lists WHERE user_id = request.user_id()
    data:
      - SELECT * FROM todos WHERE list_id = bucket.list_id
```

The `user_lists` bucket syncs first (priority 1), allowing users to see and interact with their lists immediately. The `user_todos` bucket syncs afterward (priority 2), loading in the background.

## Behavioral Considerations

* **Interruption for Higher Priority Data:** Syncing lower-priority data *may* be interrupted if new data for higher-priority buckets arrives.
* **Local Changes & Consistency:** If local writes fail due to validation or permission issues, they are only reverted after *all* data has synced.
* **Deleted Data:** Deleted data may only be removed after *all* priorities have completed syncing.
* **Data Ordering:** Lower-priority data will never appear before higher-priority data.

## Special Case: Priority 0

Priority 0 buckets sync regardless of pending uploads.

For example, in a collaborative document editing app (e.g., using Yjs), each change is stored as a separate row. Since out-of-order updates don't affect document integrity, Priority 0 can ensure immediate availability of updates.

Caution: If misused, Priority 0 may cause flickering or inconsistencies, as updates could arrive out of order.

## Consistency Considerations

PowerSync's full consistency guarantees only apply once all priorities have completed syncing.

When higher-priority data is synced, all inserts and updates at that priority level will be consistent. However, deletes are only applied when the full sync completes, so you may still have some stale data at those priority levels.

Consider the following example:

Imagine a task management app where users create lists and todos. Some users have millions of todos. To improve first-load speed:

* Lists are assigned Priority 1, syncing first to allow UI rendering.
* Todos are assigned Priority 2, loading in the background.

Now, if another user adds new todos, it's possible for the list count (synced at Priority 1) to temporarily not match the actual todos (synced at Priority 2). If real-time accuracy is required, both lists and todos should use the same priority.

## Client-Side Considerations

The client SDK APIs for tracking sync status per priority are the same for Sync Rules and Sync Streams: `waitForFirstSync(priority)`, `SyncStatus.priorityStatusEntries()`, and `SyncStatus.statusForPriority(priority)`. See [Client-Side Considerations](/sync/streams/prioritized-sync#client-side-considerations) on the Sync Streams page for details and a Flutter example.