> For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt.

# Runs

A Run records an execution of a repository action. Actions can submit batch jobs
or start applications and inference services, depending on the Site and your
Project's allocations.

## Launch work

1. Open the repository and select the branch and action you want to run.
2. Review the action's parameters, compute requirements and timeout.
3. Submit the action and open the resulting Run.
4. Follow its status as the platform prepares inputs and submits the work.

Your account must be ready at the selected Site. A pending account confirmation,
unavailable allocation or expired sign-in can prevent launch. Follow the reason
shown by the platform; a queued request is not proof that native execution has
started.

Where **Run all actions** is available, it creates a Pipeline that follows the
repository's action order. A healthy service may continue running after its
Pipeline completes.

## Inspect progress and configuration

The Run page retains the configuration accepted for that execution, including
available parameter values. Editing the action later leaves that saved record
unchanged. Older Runs may have incomplete configuration evidence.

Use the logs panel where the Site enables it. Logs are bounded and can be
truncated; they are not a complete download of every file. Slurm logs require the
Site's log collection setup. A failed service can retain a final log snapshot
when collection succeeds.

Outputs depend on the action and its publication steps. Compute may finish
successfully while a later output upload fails, so check the full Run outcome.

## Open an application

Use the Run's application link when its service is ready. Project-only access is
the default and requires current Project permission. An action can explicitly
request public access when the Site supports it.

Publishing the source repository does not publish its running application. Check
the Run's access setting before sharing its link.

## Stop or retry

Use **Stop** when you have permission and no longer need the work. Stopping is a
request: follow the Run until the platform confirms its outcome and cleanup.
If the page reports a conflicting update, refresh the current state before trying
again.

A retry may create another execution attempt. Check the previous outcome and
your inputs first. If the platform reports missing or expired member consent,
sign in again before retrying.

<details class="page-source"><summary>Page source</summary>

<a href="/source/docs/content/guides/runs.md.txt">Source snapshot</a> · Revision `f928834c8`.

</details>