# Have the error "Execute failed: Job wasn't loaded until". Unsure of meaning **URL:** \ **Category:** KNIME Business Hub\ **Created:** [February 3, 2026, 11:05am UTC](https://forum.knime.com/t/have-the-error-execute-failed-job-wasnt-loaded-until-unsure-of-meaning/91331 "2026-02-03T11:05:04Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![PeterBlack](https://forum-cdn.knime.com/letter_avatar_proxy/v4/letter/p/a88e4f/32.png) [@PeterBlack](https://forum.knime.com/u/PeterBlack)\ **Post date:** [February 3, 2026, 11:05am UTC](https://forum.knime.com/t/have-the-error-execute-failed-job-wasnt-loaded-until-unsure-of-meaning/91331/1 "2026-02-03T11:05:04Z")
I have a series of workflows on on on prem KNIME Hub. These perform an extraction of data, which then is processed by 13 workflows into the correct data shape I need. I use a workflow that calls each workflow in sequence using the “Call Workflow Service” nodes ![image](https://forum-cdn.knime.com/uploads/default/original/3X/0/8/0804e659e5fce67ff78eb71d7f4062979a87c418.png) This has been working fine, till I needed to add 3 more workflow calls. I am now receiving the “Execute failed: Job wasn’t loaded until” warning. It is not always on the same node each time. ![image](https://forum-cdn.knime.com/uploads/default/original/3X/1/3/137128d88ea176bf2375dfdf977d8bd806770c93.png) I cannot find any clear documentation on how to address this. I suspect that the cumulative effect of the nodes is exceeding capacity, so the executor is overwhelmed at a certain point but can’t be certain. Does anyone have any tips or suggestions on how to investigate or a better pattern to use for this type of workflow? ---
**Author:** ![BenceKeseru](https://forum-cdn.knime.com/letter_avatar_proxy/v4/letter/b/839c29/32.png) [@BenceKeseru](https://forum.knime.com/u/BenceKeseru)\ **Post date:** [February 5, 2026, 12:33pm UTC](https://forum.knime.com/t/have-the-error-execute-failed-job-wasnt-loaded-until-unsure-of-meaning/91331/2 "2026-02-05T12:33:47Z")
Hi! This error usually isn’t caused by a “broken” workflow, but by execution capacity and scheduling on the Hub. At some point, the context can’t start the next job quickly enough, so the node times out with \*“\*Job wasn’t loaded…” error. That also could explain why it fails on different nodes each run. Things you can try: - Check whether the execution context is overloaded and add more capacity if possible. - Reduce the number of workflow service calls (e.g. combine some steps or use Components) - Add a small delay or retry between calls. Hope this helps! ---
**Author:** ![MartinDDDD](https://forum-cdn.knime.com/user_avatar/forum.knime.com/martindddd/32/69988_2.png) [@MartinDDDD](https://forum.knime.com/u/MartinDDDD)\ **Post date:** [February 5, 2026, 12:49pm UTC](https://forum.knime.com/t/have-the-error-execute-failed-job-wasnt-loaded-until-unsure-of-meaning/91331/3 "2026-02-05T12:49:26Z")
I notice that the way you have connected your workflow with flow variables there is a lot of potential for workflows to run in parallel - what you could try and do is make it more sequential - i.e. rather than connecting flow variable from one of your “top” nodes to 3 or 4 “bottom” nodes at the same time, connect it to one, that one to the other etc… A fully sequential set up could look like this (orange arrows represent how the flow variables should connect) ![image](https://forum-cdn.knime.com/uploads/default/original/3X/0/7/0714c617dcb38e33eb7be8941a2e0044d31e864a.png) ---
**Author:** ![PeterBlack](https://forum-cdn.knime.com/letter_avatar_proxy/v4/letter/p/a88e4f/32.png) [@PeterBlack](https://forum.knime.com/u/PeterBlack)\ **Post date:** [February 11, 2026, 8:25pm UTC](https://forum.knime.com/t/have-the-error-execute-failed-job-wasnt-loaded-until-unsure-of-meaning/91331/4 "2026-02-11T20:25:34Z")
Yes, I think this is the answer. One of the workflows seems to take 24 mins which was unexpected. The local version runs quicker than this, and I think that when I am running this other scheduled processes are kicking off when I expected to have this complete before they started. I’ll look at rearranging the overall resource and scheduling so that conflicts definitely don’t happen. I hadn’t considered retry on this, which I didn’t notice before. In reality, I don’t need this to run quickly - I just need it to complete when it is run (but also, should look at optimisation). Thanks ---
**Author:** ![PeterBlack](https://forum-cdn.knime.com/letter_avatar_proxy/v4/letter/p/a88e4f/32.png) [@PeterBlack](https://forum.knime.com/u/PeterBlack)\ **Post date:** [February 11, 2026, 8:27pm UTC](https://forum.knime.com/t/have-the-error-execute-failed-job-wasnt-loaded-until-unsure-of-meaning/91331/5 "2026-02-11T20:27:25Z")
Thanks, will try rearranging this. That Programme Registration one and the RPO is a bottle neck in this and those are the most intensive workflows, so I think that these are over-running my expected time which is then resulting in clash with other scheduled processes