> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/records/results.md).

# Batch actions and results

Record actions run in the background. Queuing an action is not the same as completing it.

## Read Recent runs

Return to the Records list after starting an action. **Recent runs** shows the action, state, processed count, changed count and when it was started.

| State   | Meaning                                                                         |
| ------- | ------------------------------------------------------------------------------- |
| Queued  | The run is waiting to begin.                                                    |
| Running | Records are being processed.                                                    |
| Done    | The batch finished; some records can still have no data or individual failures. |
| Failed  | A batch-level problem prevented completion.                                     |

Processed records and changed records are different. An already-complete record may need no change; a no-match lookup may also leave it unchanged.

## Respect the limits

| Action       | Maximum records per run |
| ------------ | ----------------------: |
| Fill gaps    |                     100 |
| Enrich       |                     100 |
| Web Research |                      50 |
| Link to CRM  |                     250 |
| Push to CRM  |                     100 |

Split a larger job into intentional selections. Avoid immediately repeating a paid lookup just because a result is unchanged.

## Investigate a result

Check the selected identity, provider connection and permitted surface. For writeback, check the retained CRM link and API field names. Verify a sample record in the destination rather than inferring success from the queue notification.

If a run stays Queued or Running unexpectedly, share its action, start time and workspace with Distro support. See [Provider usage](/settings/provider-usage.md).


---

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

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

```
GET https://docs.distro.so/records/results.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 `build a script that syncs our docs to a CMS` 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.