Hops Asynchronus stuck again.....need help to understand

[Kyuubimode]

Hi,

I had an issue with hops async which I thought I solved it in the last post -

@Kyuubimode

When you have one async hops feeding input to another async hops, there is actually no input for the second hops until the first hops has finished solving. Therefore the second hops stuck in a constant solving lock.

The way to address this issue is to use a gate that stores the outputs of the first async hops and only updates the value when the it has finished solving. The second hops only gets the input after the first hops has finished solving.

However, this method stops working with there are many async hops components in the canvas. I am unable to share the gh file. I have attached a video showcasing the problem -

I am unsure why the Hops component gets stuck. Is it getting stuck because of receiving a null input for a split second? If that is the case then do I need to programmatically expire the Hops component using scripted components/ metahopper?

Why is this only happening when there are multiple hops components present in the canvas? Is there something I can do with the hops preferences? Are the max concurrent requests/ timeout/ cache/ child process counts having an effect on the hops execution? This is what it looks like right now.