Why does it keep caching after a workflow test run?

Discussion
1

A single node test works, but when the entire workflow test runs, it keeps getting stuck in caching. Seeking a solution!

2

Has this been resolved? I’m also experiencing the same problem.

3

Same question, has this been resolved? It works fine when tested in a simple workflow, but after running in a complex workflow with hundreds of nodes, it just keeps caching and doesn’t proceed.

4

This issue started occurring after I upgraded to 1.13. It’s quite random and not dependent on the simplicity or complexity of the workflow. My workflows have a maximum of just over ten nodes, and sometimes they run normally. Other times, they get stuck in the cache and won’t execute further, without producing any logs. Could official staff please investigate? We are preparing to use it in production, so it’s quite urgent. Thank you.

5

Has this problem been resolved? I encounter this problem both when previewing and running directly in the cloud and when calling the API after local deployment, and it happens quite frequently.

6

I haven’t encountered this problem since updating DIFY to version 1.13.3.