Hello! I'm running a job a fairly larger scale than before with some ops taking >1 hr to run, which is fine. However for some other faster

op

in the same

graph

, I see them "restarting" by themselves (see logs) about 4 hours after. I also see them duplicated on the graph view, which was not the case before and is, in no way, part of the graph logic. Is there some sort of hidden retry logic that may trigger this? This is a problem because the logic in the

ops

is not meant to be run twice

hmm that's weird behavior. A few questions; • what executor are you using? • do you have a retrypolicy set somewhere?

I'm using the "default" multi-process executor, and no specific retry policy, not sure what is the default one

hm by default there should be no retry policy. Are you running in a particular environment, or just locally?

Thanks I will send it to you in DM. We are running on GKE