---
title: "act: set aside run"
description: "a `SetAsideRunInput`: the run's key and a person's plain reason to the `ScrapeRun`, kept in the parked place with the reason, which the beat never takes up; each move is an event with the reason"
section: reference
address: /reference/act/set_aside_run
contract: 0476e35e6e275db5
---

# act: set aside run

a `SetAsideRunInput`: the run's key and a person's plain reason to the `ScrapeRun`, kept in the parked place with the reason, which the beat never takes up; each move is an event with the reason

[figure: The caller sends SetAsideRunInput to /v1/act/set_aside_run. The platform returns a card whose body is ScrapeRun.]

<span class="op-method">POST</span><span class="op-path">/v1/act/set_aside_run</span>

Set a run aside. The call needs the tenant rung under a token with the act grant, and it is served by the platform.

The route takes [SetAsideRunInput](/concepts/setasideruninput) and returns a card whose body is [ScrapeRun](/concepts/scraperun).



## Request body
The request body is [SetAsideRunInput](/concepts/setasideruninput).



| field | type | required | note |
|---|---|---|---|
| `run` | `text` | yes | the run's key, as the runs read lists it |
| `reason` | `text` | yes | the plain reason the run waits, which its row and its event carry |



## Response
The route returns a card whose body is [ScrapeRun](/concepts/scraperun). Every card ends with a foot that states the basis of each number, the scope of the call, and the time when the facts were true.

## Headers


| header | required | meaning |
|---|---|---|
| `Scale-Scope` | yes | the scope the call runs in: tenant/<id>, then /brand/<id>, then /strategy/<id> |
| `Scale-As-True-On` | no | the date the facts must have been true on; defaults to now |
| `Scale-As-Known-On` | no | the date the facts must have been known on; defaults to now |
| `Scale-Key` | no | for a change, the key made from the input; a repeat under the same key returns the unit held and writes nothing |



A caller needs the tenant rung and a token with the act grant. The platform serves this route.

## Example
The example sends the smallest body that SetAsideRunInput allows. The build validates it against the schema of SetAsideRunInput.

<details class="wire"><summary>Example</summary>





```sh
curl -X POST https://api.scaleintelligence.co/v1/act/set_aside_run \
  -H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/<id>" \
  -H "content-type: application/json" \
  -d '{ "run": "…", "reason": "…" }'
```




```typescript
import { client } from "@scale/sdk";
const answer = await client.act.set_aside_run({
    "run": "…",
    "reason": "…"
  });
// answer.body is a ScrapeRun. answer.foot holds the basis, the scope and the time.
```




```python
import requests
answer = requests.post("https://api.scaleintelligence.co/v1/act/set_aside_run",
    headers={"Scale-Key": KEY, "Scale-Scope": "tenant/<id>"},
    json={
      "run": "…",
      "reason": "…"
    }).json()
```




```rust
let answer: Card = client.post("https://api.scaleintelligence.co/v1/act/set_aside_run")
    .header("Scale-Key", key).header("Scale-Scope", "tenant/<id>")
    .json(&SetAsideRunInput { /* the fields of the page */ }).send().await?.json().await?;
```




</details>

## MCP tool
The MCP tool `si.act.set_aside_run` takes the same input and returns the same card. The tool changes data and needs a grant. An MCP host that renders cards draws this card from `ui://scale-intelligence/cards/ScrapeRun`. The [tool's page](/reference/tools/si-act-set_aside_run) describes it.