Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

I’m fetching a workflow from Flyte remote and find that the order of the inputs does not match the ordering of the original workflow. Is there any way to preserve this order, or somehow find the original order (from remote only)? Second question, I know the inputs/outputs have docstrings, but is it possible to fetch the workflow docstring? Will this only be possible with the new <https://github.com/flyteorg/flytekit/pull/1200|docs> changes?

1. could you share your workflow code?
2. do you want to fetch it by flyte remote? if so, we can update flyte remote

I'm afk but I believe all of our registered workflows have the input sorting issue (in both the console and when fetching from remote). I do want to fetch by remote! How would you know the original sort order from remote?

<@U019PBV483E> could you say more about “the order of the inputs does not match the ordering of the original workflow”? the inputs and outputs should be a map or dict

Pull up any workflow in the Flyte Console and you'll see that ordering of workflow inputs does not match order of the workflow function definition in code. Same with FlyteRemote calls

I was expecting them to match the order of the interface

Example:
```@workflow
def compute_average_workflow(
    seed: int = 1, count: int = 20, chunk_size: int = 5
) -&gt; float:
    fake_data_output = generate_fake_data(count=count, seed=seed)
    chunked_blobs = chunk_from_file(file_path=fake_data_output, chunk_size=chunk_size)
    computed_averages, counts_list = compute_average_for_chunks(chunks=chunked_blobs)
    aggregated_average = aggregate(averages=computed_averages, counts=counts_list)

    return aggregated_average```
The input order in the console is:

It's always alphabetical - from FlyteRemote, i'd like to somehow get that original order (seed, count, chunk_size, as is shown in the interface). Does that make sense?

I think we don’t necessarily need to sort the inputs, looking at the code

unfortunately, protobuf will automatically sort the inputs. we can add a index field <https://github.com/flyteorg/flyteidl/blob/64cabcc0a1e181f492a109760f110023ae7f3dc3/protos/flyteidl/core/interface.proto#L54-L57|here> to keep original order.

<https://github.com/flyteorg/flyte/issues/940>