it seems the issue with no module named workflows is due to using the remote.register_workflow function i registered the flow with

pyflyte register workflows --project myproject --image localhost:30000/myimage:latest

and now triggering it works

I've had the same problem and reached the same conclusion. Somehow the task/workflow code is uploaded when

pyflyte register

is used whereas if

remote.register_workflow

is used some parts of it is expected to be inside the image.

yeah i setup register_script to ci pipeline now and it works well. https://docs.flyte.org/en/latest/flytesnacks/examples/feast_integration/feast_flyte_remote.html#register-the-code

All right, thanks! I'll try that

@Jonatan Eriksson be sure to add copy_all=True parameter for register_script