# ERROR: Cannot resume build because FlowNode 57 for FlowHead 1 could not be loaded **URL:** \ **Category:** Ask a question\ **Created:** [May 3, 2024, 9:09am UTC](https://community.jenkins.io/t/error-cannot-resume-build-because-flownode-57-for-flowhead-1-could-not-be-loaded/14775 "2024-05-03T09:09:17Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![rvh](https://avatars.discourse-cdn.com/v4/letter/r/ee7513/32.png) [@rvh](https://community.jenkins.io/u/rvh)\ **Post date:** [May 3, 2024, 9:09am UTC](https://community.jenkins.io/t/error-cannot-resume-build-because-flownode-57-for-flowhead-1-could-not-be-loaded/14775/1 "2024-05-03T09:09:17Z")
I’m running into a weird error that I cant explain. I have a specific project which for which builds first finish successfully, and then afterwards get marked as Failed. The console output for that build ends with something as following: ```auto [Pipeline] End of Pipeline [Bitbucket] Notifying commit build result [Bitbucket] Build result notified Finished: SUCCESS Creating placeholder flownodes because failed loading originals. ERROR: Cannot resume build because FlowNode 57 for FlowHead 1 could not be loaded. [Bitbucket] Notifying commit build result [Bitbucket] Build result notified Finished: FAILURE ``` The time between the ‘SUCCES’ and failure can vary greatly, sometimes as short as 40minutes sometimes up to 12 hours. I have looked at the post here: [ERROR: Cannot resume build because FlowNode 19](https://community.jenkins.io/t/error-cannot-resume-build-because-flownode-19/9477) But my builds don’t show the additional part related to the performance setting. Also our Jenkins is configured to use the pipeline default (MAX\_SURVIVABILITY) already. I have even tried to add the setting manually to our JenkinsFile, but that made no difference. On the project I have had to ‘kill’ jobs at some point. Could it be that there are some historic remnants of these builds still lingering somewhere that could result in this issue? No other jobs/projects in our controller experience this issue. As additional information to the jenkins setup below. This job is the only job which is assigned to an inbound agent (running windows 11, remoting version 3206.vb\_15dcf73f6a\_9, JVM version 21.0.1+12-LTS-29 both identical to what our controller is using). I cant make much sense of the logs but something that keeps popping up that is suspicious is: ```auto May 03, 2024 7:59:34 AM WARNING org.jenkinsci.plugins.workflow.cps.CpsFlowExecution notifyListeners null java.lang.IllegalStateException: Can't send a remote FilePath to a different remote channel (current=hudson.remoting.Channel@5d28f3a7:JNLP4-connect connection from , target=null) at hudson.FilePath.writeObject(FilePath.java:3554) at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103) at java.base/java.lang.reflect.Method.invoke(Method.java:580) at com.thoughtworks.xstream.core.util.SerializationMembers.callWriteObject(SerializationMembers.java:154) Caused: com.thoughtworks.xstream.converters.ConversionException: Failed calling method ---- Debugging information ---- message : Failed calling method cause-exception : java.lang.IllegalStateException cause-message : Can't send a remote FilePath to a different remote channel (current=hudson.remoting.Channel@5d28f3a7:JNLP4-connect connection from , target=null) method : hudson.FilePath.writeObject() ------------------------------- at com.thoughtworks.xstream.core.util.SerializationMembers.callWriteObject(SerializationMembers.java:161) ``` which maybe seems related? Can anyone help me get my pipeline back to a functioning state? ## Jenkins setup: Jenkins: 2.440.3 OS: Windows 10 - 10.0 Java: 21.0.1 - Oracle Corporation (Java HotSpot™ 64-Bit Server VM) analysis-model-api:12.3.3 ant:497.v94e7d9fffa\_b\_9 antisamy-markup-formatter:162.v0e6ec0fcfcf6 apache-httpcomponents-client-4-api:4.5.14-208.v438351942757 apache-httpcomponents-client-5-api:5.3.1-1.0 asm-api:9.7-33.v4d23ef79fcc8 authentication-tokens:1.53.v1c90fd9191a\_b\_ basic-branch-build-strategies:81.v05e333931c7d bitbucket:241.v6d24a\_57f9359 bitbucket-build-status-notifier:1.4.2 blueocean:1.27.12 blueocean-bitbucket-pipeline:1.27.12 blueocean-commons:1.27.12 blueocean-config:1.27.12 blueocean-core-js:1.27.12 blueocean-dashboard:1.27.12 blueocean-display-url:2.4.2 blueocean-events:1.27.12 blueocean-git-pipeline:1.27.12 blueocean-github-pipeline:1.27.12 blueocean-i18n:1.27.12 blueocean-jwt:1.27.12 blueocean-personalization:1.27.12 blueocean-pipeline-api-impl:1.27.12 blueocean-pipeline-editor:1.27.12 blueocean-pipeline-scm-api:1.27.12 blueocean-rest:1.27.12 blueocean-rest-impl:1.27.12 blueocean-web:1.27.12 bootstrap5-api:5.3.3-1 bouncycastle-api:2.30.1.77-225.v26ea\_c9455fd9 branch-api:2.1163.va\_f1064e4a\_a\_f3 build-timeout:1.32 caffeine-api:3.1.8-133.v17b\_1ff2e0599 checks-api:2.2.0 cloud-stats:336.v788e4055508b\_ cloudbees-bitbucket-branch-source:883.v041fa\_695e9c2 cloudbees-folder:6.901.vb\_4c7a\_da\_75da\_3 clover:4.14.2.596.vb\_4d6475e990b\_ cobertura:1.17 code-coverage-api:4.99.0 command-launcher:107.v773860566e2e commons-lang3-api:3.13.0-62.v7d18e55f51e2 commons-text-api:1.11.0-109.vfe16c66636eb\_ conditional-buildstep:1.4.3 copyartifact:722.v0662a\_9b\_e22a\_c coverage:1.14.0 credentials:1337.v60b\_d7b\_c7b\_c9f credentials-binding:657.v2b\_19db\_7d6e6d custom-folder-icon:2.12 dark-theme:439.vdef09f81f85e dashboard-view:2.508.va\_74654f026d1 data-tables-api:2.0.5-1 display-url-api:2.200.vb\_9327d658781 docker-commons:439.va\_3cb\_0a\_6a\_fb\_29 docker-java-api:3.3.4-86.v39b\_a\_5ede342c docker-plugin:1.6 docker-workflow:572.v950f58993843 doclinks:0.7 dtkit-api:3.0.2 durable-task:555.v6802fe0f0b\_82 echarts-api:5.5.0-1 email-ext:1806.v856a\_01a\_fa\_39a\_ embeddable-build-status:487.va\_0ef04c898a\_2 external-monitor-job:215.v2e88e894db\_f8 favorite:2.208.v91d65b\_7792a\_c font-awesome-api:6.5.2-1 forensics-api:2.4.0 git:5.2.1 git-client:4.7.0 git-forensics:2.1.0 git-parameter:0.9.19 github:1.38.0 github-api:1.318-461.v7a\_c09c9fa\_d63 github-branch-source:1787.v8b\_8cd49a\_f8f1 gradle:2.11 gson-api:2.10.1-15.v0d99f670e0a\_7 handy-uri-templates-2-api:2.1.8-30.v7e777411b\_148 htmlpublisher:1.33 instance-identity:185.v303dc7c645f9 ionicons-api:70.v2959a\_b\_74e3cf jackson2-api:2.17.0-379.v02de8ec9f64c jakarta-activation-api:2.1.3-1 jakarta-mail-api:2.1.3-1 javax-activation-api:1.2.0-6 javax-mail-api:1.6.2-9 jaxb:2.3.9-1 jdk-tool:73.vddf737284550 jenkins-design-language:1.27.12 jjwt-api:0.11.5-112.ve82dfb\_224b\_a\_d job-dsl:1.87 joda-time-api:2.12.7-29.v5a\_b\_e3a\_82269a\_ jquery3-api:3.7.1-2 jsch:0.2.16-86.v42e010d9484b\_ json-api:20240303-41.v94e11e6de726 json-path-api:2.9.0-58.v62e3e85b\_a\_655 junit:1265.v65b\_14fa\_f12f0 ldap:725.v3cb\_b\_711b\_1a\_ef locale:431.v3435fa\_8f8445 lockable-resources:1255.vf48745da\_35d0 mailer:472.vf7c289a\_4b\_420 matlab:2.13.1 matrix-auth:3.2.2 matrix-project:822.824.v14451b\_c0fd42 mercurial:1260.vdfb\_723cdcc81 metrics:4.2.21-449.v6960d7c54c69 mina-sshd-api-common:2.12.1-101.v85b\_e08b\_780dd mina-sshd-api-core:2.12.1-101.v85b\_e08b\_780dd multiple-scms:0.8 okhttp-api:4.11.0-172.vda\_da\_1feeb\_c6e pam-auth:1.10 parameterized-trigger:787.v665fcf2a\_830b\_ pipeline-build-step:540.vb\_e8849e1a\_b\_d8 pipeline-github-lib:42.v0739460cda\_c4 pipeline-graph-analysis:216.vfd8b\_ece330ca\_ pipeline-graph-view:242.v04d14822e97f pipeline-groovy-lib:704.vc58b\_8890a\_384 pipeline-input-step:495.ve9c153f6067b\_ pipeline-milestone-step:119.vdfdc43fc3b\_9a\_ pipeline-model-api:2.2198.v41dd8ef6dd56 pipeline-model-definition:2.2198.v41dd8ef6dd56 pipeline-model-extensions:2.2198.v41dd8ef6dd56 pipeline-rest-api:2.34 pipeline-stage-step:312.v8cd10304c27a\_ pipeline-stage-tags-metadata:2.2198.v41dd8ef6dd56 pipeline-stage-view:2.34 pipeline-utility-steps:2.16.2 plain-credentials:179.vc5cb\_98f6db\_38 plugin-util-api:4.1.0 prism-api:1.29.0-13 pubsub-light:1.18 resource-disposer:0.23 role-strategy:717.v6a\_69a\_fe98974 run-condition:1.7 scm-api:690.vfc8b\_54395023 script-security:1335.vf07d9ce377a\_e snakeyaml-api:2.2-111.vc6598e30cc65 sonar:2.17.2 sse-gateway:1.26 ssh-agent:367.vf9076cd4ee21 ssh-credentials:337.v395d2403ccd4 ssh-slaves:2.948.vb\_8050d697fec sshd:3.322.v159e91f6a\_550 structs:337.v1b\_04ea\_4df7c8 terraform:1.0.10 theme-manager:215.vc1ff18d67920 thinBackup:2.0 timestamper:1.26 token-macro:400.v35420b\_922dcb\_ trilead-api:2.142.v748523a\_76693 variant:60.v7290fc0eb\_b\_cd versioncolumn:243.vda\_c20eea\_a\_8a\_f warnings-ng:11.3.0 workflow-aggregator:596.v8c21c963d92d workflow-api:1291.v51fd2a\_625da\_7 workflow-basic-steps:1058.vcb\_fc1e3a\_21a\_9 workflow-cps:3894.vd0f0248b\_a\_fc4 workflow-durable-task-step:1336.v768003e07199 workflow-job:1400.v7fd111b\_ec82f workflow-multibranch:773.vc4fe1378f1d5 workflow-scm-step:427.v4ca\_6512e7df1 workflow-step-api:657.v03b\_e8115821b\_ workflow-support:896.v175a\_a\_9c5b\_78f ws-cleanup:0.45 xunit:3.1.4 ---
**Author:** ![poddingue](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/poddingue/32/985_2.png) [@poddingue](https://community.jenkins.io/u/poddingue)\ **Post date:** [May 6, 2024, 8:26am UTC](https://community.jenkins.io/t/error-cannot-resume-build-because-flownode-57-for-flowhead-1-could-not-be-loaded/14775/2 "2024-05-06T08:26:12Z")
Hello @rvh, and welcome to this community. 👋 The error message you’re seeing suggests there’s an issue with resuming the pipeline after it has been paused or interrupted. This can happen if the build was paused and Jenkins was restarted before the build was resumed, or if there was an issue with the Jenkins controller or agent that caused the build to be interrupted. The `java.lang.IllegalStateException: Can't send a remote FilePath to a different remote channel` error suggests there’s an issue with the file path of the build. This could be due to several reasons, such as a network issue, a problem with the file system, or a configuration issue with Jenkins or the agent. ---
**Author:** ![rvh](https://avatars.discourse-cdn.com/v4/letter/r/ee7513/32.png) [@rvh](https://community.jenkins.io/u/rvh)\ **Post date:** [May 6, 2024, 9:44am UTC](https://community.jenkins.io/t/error-cannot-resume-build-because-flownode-57-for-flowhead-1-could-not-be-loaded/14775/3 "2024-05-06T09:44:57Z")
Hello @poddingue, thanks for the warm welcome and help. I’m not very experience with Jenkins yet, The issue is that the build is not paused, it was actually fully completed already when this message shows up. When you refer to ‘Jenkins’ being restarted, do you mean the controller or the agent? To debug the issue I have created builds in the same project that would run very quickly, such that I could verify that during that build, the controller nor agent would restart. Could it be that this situation happened once during a previous build, and now is still impacting newer builds on the same project somehow? I have had to ‘kill’ a build because it was preventing our controller from restarting. Could that somehow give issues now on newer builds? I saw in the documentation that this was not recommended, but could not find what the consequences could be in cases where you would do this. Is there any direction I could take to further debug the FilePath issue? I’m not very familiar with the underlying mechanisms involved so I wouldn’t really know where to start looking. either way, thank you for you reply! ---
**Author:** ![rvh](https://avatars.discourse-cdn.com/v4/letter/r/ee7513/32.png) [@rvh](https://community.jenkins.io/u/rvh)\ **Post date:** [May 6, 2024, 2:34pm UTC](https://community.jenkins.io/t/error-cannot-resume-build-because-flownode-57-for-flowhead-1-could-not-be-loaded/14775/4 "2024-05-06T14:34:02Z")
I have just been provided with credentials to remote into the system that hosts the jenkins controller. This provide me with some more information / patterns, that might be helpful in figuring out what is going on? I have found that all affected builds contain folders named both “workflow-completed” as well as “workflow-backup”. These contain 2 \<#\>.xml files with just consecutive numbers as names (e.g., 50.xml and 51.xml), where the second file will contain the text to the flownode error. The number in the filename always relates to the flownode that could not be loaded, so 51.xml will contain: Cannot resume build because FlowNode 48 for flowHead 1 could not be loaded while 27.xml will contain: Cannot resume build because FlowNode 24 for flowHead 1 could not be loaded, can be found in 27.xml. Aside from this, I also found what seemed to be an incomplete .xml file in the folder related to our develop branch with contents: ```auto develop false db0fdd14-c5f7-4541-9adb-b57a7b4369eb develop < ``` I have now removed this incomplete file in the hopes that this was maybe causing some issues, but unfortunately the issue persists. I’m also not entirely sure on how to proceed in order to repair this. ---
**Author:** ![rvh](https://avatars.discourse-cdn.com/v4/letter/r/ee7513/32.png) [@rvh](https://community.jenkins.io/u/rvh)\ **Post date:** [May 14, 2024, 8:14am UTC](https://community.jenkins.io/t/error-cannot-resume-build-because-flownode-57-for-flowhead-1-could-not-be-loaded/14775/5 "2024-05-14T08:14:55Z")
It appears as if it was an issue with the Matlab plugin. I have documented the issue on the github page of the plugin should anyone encounter similar issues: [use of runMATLABBuild in jenkinsfile, breaks builds · Issue #320 · mathworks/jenkins-matlab-plugin (github.com)](https://github.com/mathworks/jenkins-matlab-plugin/issues/320) ---
**Author:** ![poddingue](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/poddingue/32/985_2.png) [@poddingue](https://community.jenkins.io/u/poddingue)\ **Post date:** [May 14, 2024, 9:41am UTC](https://community.jenkins.io/t/error-cannot-resume-build-because-flownode-57-for-flowhead-1-could-not-be-loaded/14775/6 "2024-05-14T09:41:22Z")
Thanks for the feedback. 👍