Ironclad/rivet

[Bug]: Serious issues with subgraph splitting + running graphs via rivet-node

ai-made-approachable opened this issue · 1 comments

What happened?

I have a subgraph that is succesfully running, but the output of the subgraph returns that it has 4x not run instead.

image

Looks like if the 1st iteration is "Not ran" that all other iterations will also be "Not ran" even if that is not the case:
image
image

This issue does not happen if the 1st iteration returns something and later iterations do not return something.

What was the expected functionality?

I like to be able to use splitting + subgraph to filter data.

Describe your environment

MacOS, Node 14.0.0, etc.

Relevant log output

No response

Relevant screenshots

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Yeah, split and "Not Ran" don't interact well together, unfortunately. I'm not sure how to fix it correctly yet.