When a new pipeline has been created and detected by Gaia, it usually tries to start the pipeline and get all jobs for the detailed overview: https://github.com/gaia-pipeline/gaia/blob/master/pipeline/ticker.go#L114

Sometimes this can fail when:

• The pipeline throws runtime exceptions (e.g. dependencies are not correctly declared).
• The binary cannot be started because a dependency is missing.
• Memory limit exceeded.
• Many more reasons what can actually go wrong... 😄

We should make this more resilient and inform the user when something goes wrong.