> For the complete documentation index, see [llms.txt](https://docs.pyck.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pyck.cloud/graphql-api/queries/repositorymovements.md).

# Repository Movements

repositoryMovements Query

Returns a paginated list of RepositoryMovement objects, with optional filtering and ordering.

## Arguments

| Name      | Type                           | Description                                                            |
| --------- | ------------------------------ | ---------------------------------------------------------------------- |
| `after`   | `Cursor`                       | Returns the elements in the list that come after the specified cursor  |
| `first`   | `Int`                          | Returns the first *n* elements from the list                           |
| `before`  | `Cursor`                       | Returns the elements in the list that come before the specified cursor |
| `last`    | `Int`                          | Returns the last *n* elements from the list                            |
| `orderBy` | `RepositoryMovementOrder`      | Ordering options for RepositoryMovements returned from the connection  |
| `where`   | `RepositoryMovementWhereInput` | Filtering options for RepositoryMovements returned from the connection |

## Return Type

`RepositoryMovementConnection!` - A connection to a list of RepositoryMovement objects with pagination information.

## Notes

The `data` field contains custom movement attributes as JSON. You can use the `Data`, `DataHasKey`, `DataIn`, and `DataContains` filters to query based on JSON content. For complex JSON field queries, see [Advanced JSON Field Queries](https://github.com/pyck-ai/docs/blob/main/graphql/advanced/json-field-queries.md).

## Usage Example

```graphql
query {
  # Get pending repository movements
  repositoryMovements(
    where: { executed: false }
    orderBy: { field: CREATED_AT, direction: ASC }
    first: 10
  ) {
    edges {
      node {
        id
        repository {
          id
          name
          type
        }
        from {
          name
        }
        to {
          name
        }
        executed
        blockedBy
      }
    }
    totalCount
  }
}
```

```graphql
query {
  # Get movements for a specific repository
  repositoryMovements(
    where: { 
      repositoryID: "pallet-123",
      executedAt_GTE: "2024-01-01T00:00:00Z"
    }
  ) {
    edges {
      node {
        id
        executedAt
        from {
          name
        }
        to {
          name
        }
      }
    }
  }
}
```

## Common Filters

* `executed` - Filter by execution status
* `repositoryID` - Find movements for a specific repository
* `fromID` / `toID` - Filter by source or destination
* `blockedBy` - Find blocked movements
* `collectionID` - Find movements in a collection
* `executedAt_GTE` / `executedAt_LTE` - Filter by execution date range

## Notes

* Repository movements track the relocation of dynamic repositories
* Use this to monitor pallet movements, tote transfers, etc.
* Movements must be executed to take effect
* Can be part of collection movements for batch operations


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pyck.cloud/graphql-api/queries/repositorymovements.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.