Hi everyone! I have a scheduled flow that runs everyday successfully, but when I try to quick run it, the last task fails with the following message: Can't open lib 'ODBC Driver 17 for SQL Server' : file not found". Is there a runtime difference between scheduled run and quick run?
k
Kevin Kho
09/08/2021, 3:33 PM
Hey @Gustavo de Paula, Quick Run literally creates a run with schedule “now” so not really, unless you have a different RunConfig, or Parameters, or it’s being picked up by a different Agent than the one you expected
g
Gustavo de Paula
09/08/2021, 4:00 PM
I've found that re registering the flow fixes the problem, but after the weekend boot it comes back, making it work only when scheduled.
k
Kevin Kho
09/08/2021, 4:03 PM
What boots over the weekend? The agent?
g
Gustavo de Paula
09/08/2021, 4:06 PM
Only the pc I use to register the flow. The agent is running in a kubernetes pod that doesnt get booted
k
Kevin Kho
09/08/2021, 4:10 PM
That should be fine. I don’t know why that would affect it. And then you re-register and everything works again?
g
Gustavo de Paula
09/08/2021, 4:10 PM
exactly
k
Kevin Kho
09/08/2021, 4:16 PM
What storage do you use for the Flow and do you have other agents running?
g
Gustavo de Paula
09/08/2021, 4:19 PM
I use the azure blob storage using the
stored_as_script=True
and I have only this one agent running
k
Kevin Kho
09/08/2021, 8:39 PM
Nothing here sounds off to me. If it already lives on Azure, as long as the agent can authenticate and pick up the flow (I assume through secrets or env vars), you should be fine. After registration, nothing is needed on the host machine so a boot should not affect this, especially if it runs on Kubernetes. I assume the ODBC Driver for SQL Server is on the Kubernetes image, so that should also work fine over time.
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.