# I tried to run a new workflow but it stopped scheduling at some point... seems like a better error message is in order? **URL:** \ **Category:** usegalaxy.org support\ **Created:** [August 31, 2023, 2:07pm UTC](https://help.galaxyproject.org/t/i-tried-to-run-a-new-workflow-but-it-stopped-scheduling-at-some-point-seems-like-a-better-error-message-is-in-order/10719 "2023-08-31T14:07:06Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![bwlang](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/bwlang/32/612_2.png) [@bwlang](https://help.galaxyproject.org/u/bwlang)\ **Post date:** [August 31, 2023, 2:07pm UTC](https://help.galaxyproject.org/t/i-tried-to-run-a-new-workflow-but-it-stopped-scheduling-at-some-point-seems-like-a-better-error-message-is-in-order/10719/1 "2023-08-31T14:07:06Z")
here’s the workflow invocation in question: > **[Galaxy](https://usegalaxy.org/workflows/run?id=1983e7ce6e686957#)** > > Galaxy Workflows facilitate rigorous, reproducible analysis pipelines that can be shared with the community. I tried with the full workflow form and the new one - same result. “Invocation scheduling failed because an unexpected failure occurred.” here’s the relevant history if you want to reproduce this issue: > **[Galaxy](https://usegalaxy.org/published/history?id=207771793093ce28)** > > Galaxy is a community-driven web-based analysis platform for life science research. I _was_ able to schedule the workflow successfully if it did not check the “attempt to reuse jobs” option. ---
**Author:** ![mvdbeek](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/mvdbeek/32/110_2.png) [@mvdbeek](https://help.galaxyproject.org/u/mvdbeek)\ **Post date:** [September 1, 2023, 1:50pm UTC](https://help.galaxyproject.org/t/i-tried-to-run-a-new-workflow-but-it-stopped-scheduling-at-some-point-seems-like-a-better-error-message-is-in-order/10719/2 "2023-09-01T13:50:46Z")
Hey Brad, that’s a nice test case! We’re missing a join condition there, this shouldn’t be hard to fix, I’ll post back when it’s done. ---
**Author:** ![mvdbeek](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/mvdbeek/32/110_2.png) [@mvdbeek](https://help.galaxyproject.org/u/mvdbeek)\ **Post date:** [September 19, 2023, 5:39pm UTC](https://help.galaxyproject.org/t/i-tried-to-run-a-new-workflow-but-it-stopped-scheduling-at-some-point-seems-like-a-better-error-message-is-in-order/10719/3 "2023-09-19T17:39:13Z")
Yes, that was indeed a missing join, sorry that took a while to get to the top of the priorities. Should be fixed in [[23.1] Add missing join condition in job search by mvdbeek · Pull Request #16710 · galaxyproject/galaxy · GitHub](https://github.com/galaxyproject/galaxy/pull/16710) and is live on [usegalaxy.org](http://usegalaxy.org). ---
**Author:** ![bwlang](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/bwlang/32/612_2.png) [@bwlang](https://help.galaxyproject.org/u/bwlang)\ **Post date:** [September 19, 2023, 6:33pm UTC](https://help.galaxyproject.org/t/i-tried-to-run-a-new-workflow-but-it-stopped-scheduling-at-some-point-seems-like-a-better-error-message-is-in-order/10719/5 "2023-09-19T18:33:33Z")
I spoke too soon… invocation: `93dea09a28f88112` failed on main ![image](https://us1.discourse-cdn.com/flex020/uploads/galaxy/original/2X/6/6f705b1628384dae835f77045ec2db58dc6ef231.png) ---
**Author:** ![marten](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/marten/32/6_2.png) [@marten](https://help.galaxyproject.org/u/marten)\ **Post date:** [September 20, 2023, 9:09pm UTC](https://help.galaxyproject.org/t/i-tried-to-run-a-new-workflow-but-it-stopped-scheduling-at-some-point-seems-like-a-better-error-message-is-in-order/10719/6 "2023-09-20T21:09:01Z")
Should be fixed after [[23.1] Fix job search query by mvdbeek · Pull Request #16714 · galaxyproject/galaxy · GitHub](https://github.com/galaxyproject/galaxy/pull/16714) gets deployed. You get a golden star for identifying two bugs! ---
**Author:** ![bwlang](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/bwlang/32/612_2.png) [@bwlang](https://help.galaxyproject.org/u/bwlang)\ **Post date:** [September 24, 2023, 9:56pm UTC](https://help.galaxyproject.org/t/i-tried-to-run-a-new-workflow-but-it-stopped-scheduling-at-some-point-seems-like-a-better-error-message-is-in-order/10719/7 "2023-09-24T21:56:04Z")
Looks like this is scheduled properly now. ![image](https://us1.discourse-cdn.com/flex020/uploads/galaxy/original/2X/4/42fc1c258e9d5c7fa908cfac2239f4594a6ad383.png) yay! However, it seem’s to recalculating everything despite my selection to reuse previous jobs. Should the job reuse work in this situation? ---
**Author:** ![marten](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/marten/32/6_2.png) [@marten](https://help.galaxyproject.org/u/marten)\ **Post date:** [October 20, 2023, 4:55pm UTC](https://help.galaxyproject.org/t/i-tried-to-run-a-new-workflow-but-it-stopped-scheduling-at-some-point-seems-like-a-better-error-message-is-in-order/10719/8 "2023-10-20T16:55:54Z")
I think it should? Can you reproduce it? Please create an issue on the github repo.