Runs and Logs

Every dispatched workflow creates a workflow run with one or more jobs. Trylle retains run state independently of the runner queue, so completed history and recorded job results survive service restarts.

Use the dashboard

Open a repository and select Actions to view recent workflow runs. The list shows the workflow, ref, event, actor, status, and update time. Select a run to inspect its dependency graph, jobs, duration, and artifacts.

Common states are:

The run graph follows needs dependencies. Select an individual job or step to read its output, failure reason, and timing.

Read logs from the CLI

List recent runs for an explicit repository and select the exact run ID:

try ci list -R OWNER/NAME --limit 20

Read run details:

try ci view RUN_ID

Print the available logs:

try ci logs RUN_ID

Re-run try ci view or try ci logs when you need fresh state. On CLI 1.0.0, try ci watch and try ci logs --follow return the current payload rather than continuously polling.

Live and completed logs

While a job is active, Trylle reads the latest available Actions task and feed logs. Some command output may become visible only after the underlying runner command completes. Refresh the job log view when a long-running step finishes.

After completion, Trylle serves the retained stdout/stderr snapshot and archived log bundle. A temporary runner or dashboard interruption does not change the recorded final job state.

Do not print secrets deliberately. Repository secrets and correctly classified secret values are supplied as masking hints, but masking should be a last line of defense rather than a reason to echo credentials.

Cancel a run

Confirm that the selected run is still queued or running:

try ci view RUN_ID

Then cancel it:

try ci cancel RUN_ID

The dashboard also exposes Cancel workflow on active runs. Cancellation propagates to queued and running child jobs; already completed jobs retain their results.

Artifacts

Artifacts created by actions/upload-artifact appear in the run's Artifacts section. Select an artifact to download its archive. actions/download-artifact can pass artifacts to a dependent job in the same workflow.

- uses: actions/upload-artifact@v4
  with:
    name: test-results
    path: test-results/
    if-no-files-found: error

Use artifacts for build outputs, reports, and files needed by another job. Keep credentials and other sensitive values out of uploaded directories.

Diagnose a missing or unexpected run

Check these causes in order:

1. Actions policy: the repository may be disabled, .github/workflows may be excluded, or the workflow path may be individually disabled.
2. Event support: only push and pull_request dispatch automatically; workflow_dispatch is manual.
3. Filters: branch, tag, action-type, or path filters may exclude the event.
4. Pull request path comparison: if Trylle cannot resolve changed paths, path-filtered workflows are skipped.
5. Runner selector: Windows and unknown labels are skipped.
6. Workflow validation: dynamic matrices and job-level containers are unsupported.

Use the compatibility table when a workflow works on GitHub but does not dispatch or plan on Trylle.