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

# Debugging GitHub Actions

Namespace gives you direct access to your running workflows and deep visibility into their performance.
Reach for interactive access when you need to get inside a job as it runs, remote display when you need a graphical session, performance metrics and logging when you are analyzing a run after the fact, OOM detection and crash dumps when a job fails unexpectedly, and queue time when jobs are waiting to start.

> [card] [Interactive access](https://namespace.so/docs/solutions/github-actions/debugging/interactive-access.md)
>
> Pause a running job, set breakpoints, and SSH into the runner instance.

> [card] [Remote display](https://namespace.so/docs/solutions/github-actions/debugging/remote-display.md)
>
> VNC into macOS runners and RDP into Windows runners.

> [card] [Performance metrics](https://namespace.so/docs/solutions/github-actions/debugging/performance-metrics.md)
>
> Correlate job steps with CPU, memory, disk, and network metrics and compare against previous runs.

> [card] [Advanced logging](https://namespace.so/docs/solutions/github-actions/debugging/logging.md)
>
> Container logs, build logs, and step-to-metric correlation beyond standard GitHub Actions logs.

> [card] [OOM detection](https://namespace.so/docs/solutions/github-actions/debugging/oom-detection.md)
>
> Make out-of-memory conditions explicit instead of guessing from allocation graphs.

> [card] [Crash dumps](https://namespace.so/docs/solutions/github-actions/debugging/crash-dumps.md)
>
> Automatically collect crash dumps and store them as artifacts for forensic analysis.

> [card] [Queue time](https://namespace.so/docs/solutions/github-actions/debugging/queue-time.md)
>
> Investigate queue time with the insights view and concurrency usage.

## Hands-on support

Got stuck? Need help with debugging one of your workflows? Our team is here to assist:

* **Technical Support**: Reach out to [support@namespace.so](mailto:support@namespace.so) to talk to one of our engineers.
* **Community**: Join our community [Discord](https://discord.gg/DqMzDFR6Hc) to learn about tips and best practices.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.