> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trunk.io/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

> Reliability, forks, and other common questions about Dynamic CI.

## Reliability

> [accordion] What happens if Trunk is slow or down?
>
> Every job runs. The action is built to retry for resiliency, but if Trunk is
> down, the action will fail open and all your jobs will run.

> [accordion] What does the Buildkite plugin do if Trunk is unavailable?
>
> It uploads your pipeline unchanged, so every step runs.

> [accordion] What happens to a job Trunk has never seen?
>
> It runs. A job needs a couple of days of history before Trunk will
> recommend skipping it.

> [accordion] Can Dynamic CI skip a job in my merge queue?
>
> Only when a paths filter you configured excludes it. See
> [Merge queues](https://docs.trunk.io/ci/dynamic-ci/merge-queue.md).

> [accordion] Can I make sure a skipped job runs before a pull request enters the queue?
>
> Yes. Set the job to [Run Before Queue](https://docs.trunk.io/ci/dynamic-ci/run-before-queue.md).
> Trunk starts it on the head commit before the pull request enters the
> queue, unless it already ran there.

> [accordion] Why is my pull request held with a Run Before Queue line?
>
> Trunk is starting its Run Before Queue jobs on the head commit. If the
> line says **Run Before Queue failed to start**, force the jobs and rerun,
> or push. See [Failed to start](https://docs.trunk.io/ci/dynamic-ci/run-before-queue.md#failed-to-start).

## Forks

> [accordion] What happens on pull requests from forks?
>
> A pull request from a fork has no access to your repository's secrets, so
> the filter job has no token and every job runs.

> [accordion] Does Run Before Queue work on pull requests from forks?
>
> No. Dynamic CI runs every job on them.
