Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Bug][Blueprint] Scheduled run fails silently when plan generation errors

Abierto
  • ¿Algo no está bien?
#9,232 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 3 días

@jcamargos ya está trabajando en esto.

Desde el 18/10/2026.

  • #9234 de @jcamargos — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github, go
Área
backend

Línea de trabajo

Start at BlueprintJob.Run in backend/server/services/blueprint.go and follow the call to createPipelineByBlueprint, where the MakePlanForBlueprint error returns before any pipeline record is created. The maintainers have not chosen how the failure should surface, so confirm the approach in the thread before coding. Done means a scheduled run that fails at plan time leaves a visible failed record, and a test covers the cron path.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Search before asking
  • I had searched in the issues and found no similar issues.
What happened

When a scheduled (cron) blueprint run fails during plan generation, the failure is only logged. BlueprintJob.Run in backend/server/services/blueprint.go calls createPipelineByBlueprint, which returns the MakePlanForBlueprint error before any pipeline is created. No pipeline record exists, so nothing shows as a failed run in the UI, and alerting on pipeline status can't catch it. The only trace is the lake log:

[blueprint] run cron job failed on blueprint:[1][my-blueprint]
caused by: ...

This is plugin-agnostic: any error raised while making the plan (e.g. a data source rejecting credentials) is handled this way. Example cause: #9220.

What do you expect to happen

A scheduled run that fails at plan time is visible the same way a failed pipeline is: in the UI and to anything monitoring pipeline status. Recording it as a failed pipeline is one option; maintainers may prefer another.

How to reproduce
  1. Create a GitHub App connection and a blueprint using it, with a cron schedule.
  2. Set the DevLake host clock about 2s ahead of real time (see #9220).
  3. Wait for the scheduled run.
  4. No new pipeline appears; the error is only in the lake log.
Anything else

Manually triggering the same blueprint (POST /blueprints/:id/trigger) returns the error to the caller, so only scheduled runs are affected.

Version

v1.0.3-beta14 (same code on main)

Are you willing to submit PR?
  • Yes I am willing to submit a PR!
Code of Conduct
Lenguaje dominante
Go
Estrellas
3.2k
Forks
824
Merge medio
3 d 17 min
PR fusionados (30 d)
48

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de apache/devlake

Todos los issues de apache/devlake

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.