Thread
#prefect-community
    j

    Jehan Abduljabbar

    2 months ago
    Good morning, I've got this issue. I am using LocalDaskExecuter() and Git Storage. When I run the flow in the cloud, dask breaks down a task into multiple ones, with new labels. But the flow in Git storage doesn't recognize the new tasks, which gives me a mismatch error between the flow version stored in prefect backend and the flow version in storage. How do I get around that?
    Anna Geller

    Anna Geller

    2 months ago
    to get around that, you would need to commit and push your code to GitHub and then possibly reregister your flow if any metadata changed since then
    j

    Jehan Abduljabbar

    2 months ago
    But it is changing as the flow run is taking place in the cloud.
    Anna Geller

    Anna Geller

    2 months ago
    you have to commit your code and push it to your GitHub storage then, Prefect can grab the latest version of your flow at runtime
    j

    Jehan Abduljabbar

    2 months ago
    That is what I'm already doing
    Anna Geller

    Anna Geller

    2 months ago
    hard to say what's wrong, could you perhaps create a minimal reproducible example repository describing your approach and the issue and share it?