# Triggered Runs
source: https://docs.chalk.ai/docs/runs

## Execute resolver runs via API

In addition to scheduling resolver executions,
Chalk allows you to trigger resolver executions programmatically via the Chalk Client, CLI and REST API.

### Trigger a Run via Chalk Client

Using the Chalk Client, you can trigger a resolver run using the trigger_resolver_run command.

```
from chalk.client import ChalkClient

ChalkClient().trigger_resolver_run(resolver_fqn="load_user_data", store_online=True)
```

To read more about how to specify parameters like upper_bound, lower_bound, store_online, store_offline,
and idempotency_key, check out our API documentation.

### Trigger a Run via CLI

The chalk trigger command allows you to trigger a resolver execution via the CLI.

```
$ chalk trigger --resolver my.module.fn
ID:     j-2qtwuxpskm2pbg
Status: Received
URL:    https://chalk.ai/runs/j-2qtwuxpskm2pbg
```

To read more about how to specify flags like deployment, persist-online, persist-offline, and
idempotency-key, check out our CLI documentation.

### Trigger a Run via API

Using the trigger API endpoint allows you to build custom integrations with other
data orchestration tools like Airflow.

The trigger endpoint will return within 300 seconds, even if the
triggered run takes longer to execute. If the returned status is received,
you should poll the v1/runs/{id} endpoint until status transitions to succeeded or failed.

It is also possible to manually trigger resolver executions via the Chalk dashboard, on the
details page for the resolver you would like to run. The same input parameters are available in the dashboard.

Note: if you use a user-scoped token (i.e. one that's derived from chalk login) you will need to
specify the environment in which to trigger your resolver via the X-Chalk-Env-id header.

### Trigger a run

The fully qualified name of the resolver to trigger. Example: 'neobank.resolvers.offline_get_transactions'.

The lower bound timestamp to use when sampling input features to run this resolver on. Example: '2021-01-01T00:00:00Z'.

The upper bound

The maximum number of samples to pull from the offline store when running this resolver. Example: 1000.

### Response

ID of the relevant run.

One of 'received', 'succeeded', or 'failed'

### Example

```
curl -XPOST -H "Authorization: Bearer $(chalk token)" \
     -H "X-Chalk-Env-Id: <your-environment-id>" \
     -H "Content-Type: application/json" \
     https://api.chalk.ai/v1/runs/trigger \
     -d '{ "resolver_fqn": "neobank.resolvers.offline_get_transactions" }'

# Returns

{
  "id": "<run-id>",
  "status": "succeeded"
}
```

### Query run status

URL Param. ID of the relevant run.

### Response

ID of the relevant run.

One of 'received', 'succeeded', or 'failed'

### Example

```
curl -H "Authorization: Bearer $(chalk token)" \
     -H "X-Chalk-Env-Id: <your-environment-id>" \
     https://api.chalk.ai/v1/runs/{run_id}
```