> ## 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.

# Queue Time

export const CenteredImage = ({src, alt, width, caption, className}) => {
  const [basePath, setBasePath] = useState("");
  useEffect(() => {
    const path = window.location.pathname;
    setBasePath(path === "/docs" || path.startsWith("/docs/") ? "/docs" : "");
  }, []);
  return <Frame caption={caption} className={className} style={{
    maxWidth: width,
    marginInline: "auto"
  }}>
			<OptimizedImage src={`${basePath}${src}`} alt={alt} />
		</Frame>;
};

When jobs wait before starting, use the insights view and concurrency usage to understand why.

The [insights view](https://cloud.namespace.so/workspace/ghrunners/insights) offers comprehensive performance analytics of your jobs over time.
By default, the explorer displays your job durations, but you can also understand the queue time by changing the view on the top right.
If you are investigating a recent case of surprisingly long queue time, adjust the timeframe to match your investigation.

<CenteredImage width={600} alt="Queue time insights" src="/docs/images/github-actions/queue-time.webp" />

The most common reason for queue time is that you are hitting your concurrency limits.
You can see the concurrent resource usage in the [usage dashboard](https://cloud.namespace.so/workspace/usage/concurrency).

<CenteredImage width={600} alt="Concurrent resource usage" src="/docs/images/github-actions/concurrent-resource-usage.webp" />

If you are frequently reaching your resource limits, you may benefit from a larger plan. We'd be happy to put a custom plan together for you.
Reach out to our [Sales Team](mailto:sales@namespace.so) for custom plans that scale up to thousands of vCPUs and TBs of RAM.

## Next steps

* [Debugging overview](/docs/solutions/github-actions/debugging)
* [Performance metrics](/docs/solutions/github-actions/debugging/performance-metrics)