You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@fopina The reproduction jobs by themselves will cause an error because job1 has a non-existent dependent job job. But if that is resolved, the dependent job still does not run.
This happens because the dependent job that is resolved does not have an agent object associated with it. I'm seeing this happen with scheduled and manual trigger.
Odd, I thought there was a test in place to check dependent jobs...
Describe the bug
Dependent jobs are not triggered
To Reproduce
Steps to reproduce the behavior:
job1
Expected behavior
job2
to be executed** Specifications:**
Additional context
dkron executed with
Output from the moment job1 was kicked
The text was updated successfully, but these errors were encountered: