Order of workflows in configuration

[jingyunc]

Does the order of workflow registration in configuration represent the order of workflow execution?

For example, in NVFlare/job_templates/swarm_cse_pt/config_fed_server.json, two workflows were registered:

"workflows": [
    {
      "id": "swarm_controller",
      "path": "nvflare.app_common.ccwf.SwarmServerController",
      "args": {
        "num_rounds": 3
      }
    },
    {
      "id": "cross_site_eval",
      "path": "nvflare.app_common.ccwf.CrossSiteEvalServerController",
      "args": {
        "eval_task_timeout": 300
      }
    }
  ]

Does that mean the swarm_controller will always ran before cross_site_eval?

If I register another workflow in between, like:

"workflows": [
    {
      "id": "swarm_controller",
      "path": "nvflare.app_common.ccwf.SwarmServerController",
      "args": {
        "num_rounds": 3
      }
    },
    {
      "id": "my_workflow",
      "path": "my_path",
      "args": {}
    },
    {
      "id": "cross_site_eval",
      "path": "nvflare.app_common.ccwf.CrossSiteEvalServerController",
      "args": {
        "eval_task_timeout": 300
      }
    }
  ]

Would my_workflow run after swarm_controller and before cross_site_eval?

Thanks.

[SYangster]

Yes, this is correct. For example in the logs you can see when the first workflow ends and the next starts:

2023-10-27 12:12:03,902 - SwarmServerController - INFO - [identity=simulator_server, run=simulate_job, wf=swarm_controller]: Workflow swarm_controller done!
2023-10-27 12:12:03,902 - ServerRunner - INFO - [identity=simulator_server, run=simulate_job, wf=swarm_controller]: Workflow: swarm_controller finalizing ...
2023-10-27 12:12:04,280 - ServerRunner - INFO - [identity=simulator_server, run=simulate_job, wf=swarm_controller]: starting workflow cross_site_eval (<class 'nvflare.app_common.ccwf.cse_server_ctl.CrossSiteEvalServerController'>) .