When deploying nested workflows, another "system" workflow NetworkWorkflow is started under the hood to provide a map workflow<-->service. This workflow has no timeout set, defaulting to 10s. But if the overall deployment requires more than 10 seconds to run, NetworkWorkflow will exit before the deployment can finish, causing #320
We should probably review the strategy of NetworkWorkflow, specially when nested workflows are involved, but for the time being this fix should be good.
I didn't find a way to meaningfully unit test this, and a proper e2e test would take >10s so I propose we don't test it.
coverage: 65.5%. remained the same
when pulling 82da594384a448e136ea9a01af2a740c22afa0d2 on massi/320
into 0cfab66d73436c7678ad02e078958e4061059faf on main.
Fixes #320
When deploying nested workflows, another "system" workflow
NetworkWorkflow
is started under the hood to provide a map workflow<-->service. This workflow has no timeout set, defaulting to 10s. But if the overall deployment requires more than 10 seconds to run,NetworkWorkflow
will exit before the deployment can finish, causing #320We should probably review the strategy of
NetworkWorkflow
, specially when nested workflows are involved, but for the time being this fix should be good.I didn't find a way to meaningfully unit test this, and a proper e2e test would take >10s so I propose we don't test it.