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

# workflowIsAssignable

Returns whether the given workflow execution is currently assignable.

Audience: Programmer

Returns whether the given workflow execution is currently assignable.

Reads the `pyck_workflow_is_assignable` Temporal search attribute on the execution. Workflows that never wrote the attribute are treated as assignable (returns `true`) — matching the SDK's default behaviour for workflows that didn't opt in via `workflowsdk.WorkflowIsAssignableSetter`.

**Served by:** [workflow](https://docs.pyck.cloud/graphql-api/services/workflow.md)

## Arguments

| Name    | Type                                                                                                        | Default | Description |
| ------- | ----------------------------------------------------------------------------------------------------------- | ------- | ----------- |
| `input` | [GetWorkflowIsAssignableInput](https://docs.pyck.cloud/graphql-api/inputs/getworkflowisassignableinput.md)! |         |             |

## Returns

[GetWorkflowIsAssignableResponse](https://docs.pyck.cloud/graphql-api/types/getworkflowisassignableresponse.md)!

## Example

Returns whether a given workflow execution currently advertises itself as assignable via the pyck\_workflow\_is\_assignable search attribute. Workflows that never wrote the attribute are treated as assignable (returns true).

```graphql
query GetWorkflowIsAssignable($input: GetWorkflowIsAssignableInput!) {
  workflowIsAssignable(input: $input) {
    isAssignable
  }
}
```

**Variables**

```json
{
  "input": {
    "workflowExecutionID": "<run ID>",
    "workflowID": "<workflow execution ID>"
  }
}
```


---

# 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/workflowisassignable.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.
