# Issues with fusion

**URL:** https://community.seqera.io/t/issues-with-fusion/2091
**Category:** Ask for help
**Tags:** nextflow, aws, fusion
**Created:** [April 24, 2025, 3:17am UTC](https://community.seqera.io/t/issues-with-fusion/2091 "2025-04-24T03:17:09Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![ka\_li](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/ka_li/32/1777_2.png) [@ka\_li](https://community.seqera.io/u/ka_li)
#### Post date: [April 24, 2025, 3:17am UTC](https://community.seqera.io/t/issues-with-fusion/2091/1 "2025-04-24T03:17:09Z")

</div>

Hi, all. I have been using nextflow version `24.10.3` to run my pipelines, which utilize the AWS `EKS` to execute processes. Until recently, everything was working fine.  
However, I have started encountering issues where the pipeline no longer runs as expected. The specific error message is shown in the attached screenshot. From the error message, it may be related to `fusion`.

**Environment Information:**

- AWS EKS Version: 1.31
- Nextflow Version: 24.10.3

After some troubleshooting, I found that downgrading nextflow to version `24.04.2` resolves the issue.  
Have there been some recent changes to fusion? Has anyone else experienced a similar problem? If so, how did you resolve it? Any insights or suggestions would be greatly appreciated.

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/seqera/original/2X/a/abd4e3c8ea636520936166c9769bc80aa0462bc5.jpeg)