microscopic-school-54375
02/22/2023, 12:43 PMtall-lock-23197
freezing-airport-6809
acceptable-policeman-57188
freezing-airport-6809
disabled
or removed from the config
. If so Flyte thinks there is no rule and so schedules it randomlyfreezing-airport-6809
microscopic-school-54375
02/28/2023, 7:46 AMmicroscopic-school-54375
02/28/2023, 8:24 AMmicroscopic-school-54375
03/02/2023, 1:59 PMpyflyte run
time already.
So maybe it is time to challenge some assumptions (I hope you can forgive me for the ping @acceptable-policeman-57188 @average-finland-92144 and @freezing-airport-6809 - you have been so helpful in the past. 🫶).
• I was hoping that a workflow can be applied, EVEN when the cluster that shall run it is not available at that time. For example I was able to apply --remote runs when the control plane had 0 data plane clusters connected. Once the data plane cluster came online, runs would get scheduled. I saw that there was a concept for retries, which gave me hope that this would work 😅
• More directly phrased, can one of you explain (or point me towards docs) if there is some kind of persistence layer for runs, before they get scheduled to data plane clusters / propellerfreezing-airport-6809