curious if anyone has seen this before. I'm exposing my flyte workflows to be called downstream by another workflow. If the upstream workflow is of type workflow i have no issues, however if i change the upstream to be the default launchplan i get the following in the downstreams compile step

File "/app/workflows/royalties/agg_input_validations_workflow.py", line 34, in <module>
    ) -> typing.Tuple[str, dict]:
  File "/home/jovyan/.local/lib/python3.7/site-packages/flytekit/core/workflow.py", line 737, in workflow
    return wrapper(_workflow_function)
  File "/home/jovyan/.local/lib/python3.7/site-packages/flytekit/core/workflow.py", line 733, in wrapper
    workflow_instance.compile()
  File "/home/jovyan/.local/lib/python3.7/site-packages/flytekit/core/workflow.py", line 613, in compile
    workflow_outputs = exception_scopes.user_entry_point(self._workflow_function)(**input_kwargs)
  File "/home/jovyan/.local/lib/python3.7/site-packages/flytekit/common/exceptions/scopes.py", line 207, in user_entry_point
    raise FlyteScopedUserException(*_exc_info())
flytekit.common.exceptions.scopes.FlyteScopedUserException: Input was not specified for: scenario_name of type simple: STRING

entirely possible there’s a bug here.

i think it is actually