---
title: "Bytesize: Troubleshooting a failed pipeline"
description: "A popular nf-core/bytesize talk about how to debug a failed Nextflow run"
url: "https://phil.ewels.co.uk/talks/2022/03/01/bytesize_debugging_pipeline_runs"
site: "phil.ewels.co.uk"
author: "Phil Ewels"
section: "Talks"
type: "Bytesize"
date: "2022-03-01"
location: "Online"
event: "https://nf-co.re/events/2022/bytesize-35-debugging-pipeline"
slides: "https://phil.ewels.co.uk/talks/2022/03/01/bytesize_debugging_pipeline_runs/bytesize_31_-_debugging.pdf"
video: "https://www.youtube.com/watch?v=z9n2F4ByIkY"
---

# Bytesize: Troubleshooting a failed pipeline

> A popular nf-core/bytesize talk about how to debug a failed Nextflow run

In the nf-core community we spend a lot of time helping people with problems that
they've hit when running Nextflow pipelines.

In this talk, I went over some of the more common failures and how best to troubleshoot these.
Importantly, I described where to start looking for issues and how to ask for help in the most effective way.

This bytesize talk has been referred to many times and was eventually
written up as a [documentation page](https://nf-co.re/docs/usage/troubleshooting) on the nf-core website.

---

From the personal website of Phil Ewels, a software developer and bioinformatician in Stockholm, Sweden: https://phil.ewels.co.uk/
The whole site as Markdown: https://phil.ewels.co.uk/llms.txt