Setup Runs not catching Fly-driven model changes?

Hello. I’m using Fly to build a set of parametric (energy model) runs, using the Record component to queue them, and then sending them to Pollination. But all results are coming back identical from the cloud. I notice the #model:PATH (json) is identical across all the setup runs…could this be an issue?

Hi @novellin,

Thank you for the detailed explanation. It looks like you are missing the part for setting a unique name for each model. Otherwise they will overwrite each other. You can use the record id as an input to set it up.

(facepalm). I expected what I was missing to be silly; It often is. That is an extra-silly miss.

Wrinkle: the simple connection (i.e. your screenshot) doesn’t work for me, which makes sense because that’s trying to name the same model n different names. What does appear to work is sending the most-recent record to the _name port, like so:

Could some complexity elsewhere in my script confound some intelligence in the Fly output?

Oops! My bad. You should use the id output. I dropped the wrong component here.

Have you watched this video? I believe I cover all the details for a basic workflow in the video.