Repository navigation
Webhook not firing on schedule #161
Replies: 4 comments
|
I am unable to reproduce this. Can you please submit a bug report using GitHub Issues, and provide more information? In particular, please show me the completed job, which should list all the actions it ran:
Does your completed job not show any actions? Is the completed job actually the correct event with your actions attached to it? Here is a potential point of confusion. You mentioned this was a workflow, but remember that workflows launch sub-jobs, which do not run the actions, unless you specifically attach actions to the nodes in the workflow map editor. So, if you added actions to the workflow itself, then only that completed outer parent workflow job will show the actions on the job detail screen. |
|
Done. On a separate note, this is such a great improvement on Cronicle. So easy for me to migrate over. Thanks for all the hard work |
|
i'm an idiot. the trigger one is not correct.
You're the best
February 25, 2026 at 12:36 PM, "Joseph Huckaby" ***@***.*** ***@***.***?to=%22Joseph%20Huckaby%22%20%3Cnotifications%40github.com%3E > wrote:
…
I am unable to reproduce this. Can you please submit a bug report using GitHub Issues https://github.com/pixlcore/xyops/issues , and provide more information?
In particular, please show me the completed job, which should list all the actions it ran:
Screenshot.2026-02-25.at.9.31.03.AM.png (view on web) https://github.com/user-attachments/assets/a9bbe036-0eee-4c0e-9b4c-192bb07df52f
Does your completed job not show any actions? Is the completed job actually the correct event with your actions attached to it?
Here is a potential point of confusion. You mentioned this was a workflow, but remember that workflows launch sub-jobs, which **do not run the actions**, unless you specifically attach actions to the nodes in the workflow map editor. So, if you added actions to the workflow itself, then only that completed outer parent workflow job will show the actions on the job detail screen.
—
Reply to this email directly, view it on GitHub #161 (comment) , or unsubscribe https://github.com/notifications/unsubscribe-auth/AAE6CFHYFW7RDATOOYCJ2AD4NXMQXAVCNFSM6AAAAACV7GUL3KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKOJSGU3TOMQ .
You are receiving this because you authored the thread.
|
|
ok. don't close yet. some triggers have the right variable and aren't hitting the api. let me inspect a little more.
Thanks for you assistance and patience
February 25, 2026 at 12:36 PM, "Joseph Huckaby" ***@***.*** ***@***.***?to=%22Joseph%20Huckaby%22%20%3Cnotifications%40github.com%3E > wrote:
…
I am unable to reproduce this. Can you please submit a bug report using GitHub Issues https://github.com/pixlcore/xyops/issues , and provide more information?
In particular, please show me the completed job, which should list all the actions it ran:
Screenshot.2026-02-25.at.9.31.03.AM.png (view on web) https://github.com/user-attachments/assets/a9bbe036-0eee-4c0e-9b4c-192bb07df52f
Does your completed job not show any actions? Is the completed job actually the correct event with your actions attached to it?
Here is a potential point of confusion. You mentioned this was a workflow, but remember that workflows launch sub-jobs, which **do not run the actions**, unless you specifically attach actions to the nodes in the workflow map editor. So, if you added actions to the workflow itself, then only that completed outer parent workflow job will show the actions on the job detail screen.
—
Reply to this email directly, view it on GitHub #161 (comment) , or unsubscribe https://github.com/notifications/unsubscribe-auth/AAE6CFHYFW7RDATOOYCJ2AD4NXMQXAVCNFSM6AAAAACV7GUL3KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKOJSGU3TOMQ .
You are receiving this because you authored the thread.
|

Uh oh!
There was an error while loading. Please reload this page.
I have a webhook set up for multiple jobs that is set to fire on startup, success, and failure (the last is a slightly different webhook). When I manually trigger the jobs, they fire, but do not do so when the workflow is run on a schedule.
All reactions