abstrask opened a new issue, #9232: URL: https://github.com/apache/devlake/issues/9232
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/devlake/issues?q=is%3Aissue) 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 blueprint with a cron schedule and a connection whose credentials will fail at plan time (e.g. a GitHub App connection with an invalid private key). 2. Wait for the scheduled run. 3. 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 - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
