Pablo Casares
Pablo Casares
We are already setting https://github.com/flyteorg/flyte/blob/876999ca9c64025315b52d2d5b04195c530fa3df/flytepropeller/propeller-config.yaml#L48 in our setup. Would the get() operation I mentioned help there?
Hi @pvditt, thank you for taking a look at this. We noticed the issue in workflows that have external subworkflows via launch plans. We weren't able to reproduce it either...
- Were you able to determine if the parent workflow was still getting executed by propeller or was it just the console showing it as running? The parent workflow was...
Hi again @pvditt, I checked the logs and I can see that message happening when we had propeller v1.12.0 and even now with v1.11.0. Seems to be happening several times...
Hi @pvditt thanks for the update. I did a quick search on the logs and I found only 1 line with the parent wf execution id: ``` SELECT * FROM...
Thank you for working on this. Once the next release is available I can test this and I'll report back if the issue is solved.