> 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/types/repositorymovement.md).

# RepositoryMovement

RepositoryMovement Type

Represents a movement of a repository (like a pallet or tote) from one location to another within the warehouse.

## Fields

| Field          | Type                          | Description                                   |
| -------------- | ----------------------------- | --------------------------------------------- |
| `id`           | `ID!`                         | Unique identifier of the repository movement  |
| `tenantID`     | `UUID!`                       | Tenant identifier                             |
| `dataTypeID`   | `UUID`                        | Data type identifier                          |
| `dataTypeSlug` | `String`                      | Data type slug                                |
| `data`         | `Map`                         | Custom data associated with the movement      |
| `createdAt`    | `Time!`                       | Creation timestamp                            |
| `createdBy`    | `UUID!`                       | User identifier who created the movement      |
| `updatedAt`    | `Time`                        | Last update timestamp                         |
| `updatedBy`    | `UUID`                        | User identifier who last updated the movement |
| `deletedAt`    | `Time`                        | Deletion timestamp                            |
| `deletedBy`    | `UUID`                        | User identifier who deleted the movement      |
| `repositoryID` | `ID!`                         | ID of the repository being moved              |
| `fromID`       | `ID`                          | Source repository ID (parent location)        |
| `toID`         | `ID!`                         | Destination repository ID (parent location)   |
| `executed`     | `Boolean!`                    | Whether the movement has been executed        |
| `executedAt`   | `Time`                        | Execution timestamp                           |
| `handler`      | `String!`                     | The handler responsible for the movement      |
| `blockedBy`    | `RepositoryMovementBlockedBy` | Reason why the movement is blocked            |
| `collectionID` | `UUID`                        | ID of the collection movement this belongs to |
| `orderID`      | `UUID`                        | Associated order ID                           |
| `position`     | `Int!`                        | Position in execution order                   |
| `from`         | `Repository`                  | Source repository object                      |
| `to`           | `Repository!`                 | Destination repository object                 |
| `repository`   | `Repository!`                 | The repository being moved                    |

## Interfaces

* `Node`

## Usage Example

```graphql
query {
  repositoryMovements(
    where: { executed: false }
    orderBy: { field: CREATED_AT, direction: DESC }
  ) {
    edges {
      node {
        id
        repository {
          name
          type
        }
        from {
          name
        }
        to {
          name
        }
        executed
        blockedBy
        handler
      }
    }
  }
}
```

## Notes

* Repository movements track the relocation of dynamic repositories (pallets, totes, trolleys)
* The `repositoryID` refers to the repository being moved (e.g., a pallet)
* The `fromID` and `toID` refer to the parent repositories (e.g., warehouse zones)
* Movements must be executed to take effect
* Can be blocked for various reasons (hazardous materials, regulatory holds, etc.)
* Often part of collection movements for coordinated execution


---

# 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/types/repositorymovement.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.