[🐛 BUG] Function field emtpy when trying to submit multiple worklfows about taipy

[FlorianJacta]

Hi @Ginzou-3, why are you stopping the Core service and loading two different configurations?

Try to create only one configuration/TOML and load it once in your if __name__ == "__main__". Same thing for the run method. It should only be run once in your if __name__ == "__main__" and never stopped.

If not possible, please tell us what is your use case so we can understand it a bit better.

[Ginzou-3]

Hm okay i thought the config is like a changeable disk, like when i want to listen to another band, i change the CD.
For me a toml file was like a workflow. When I have a different workflow a change my toml. Thats why i stop my core, because i cant alter the config file when its running.

Idea: Get request for workflow 1 -> taipy loads the config -> let the scenario run -> return the output -> request for workflow 2 -> core stop -> load new config -> etc

[FlorianJacta]

The configuration is how you configure your application overall. Inside a unique application/configuration, you can have different workflows/scenarios.

@jrobinAV If you have anything to say, please do.

[jrobinAV]

Not much to add...
The Config has been created to support multiple workflows (They are called ScenarioConfig).
If you want to create multiple workflows, you can create multiple ScenarioConfig in the global Config singleton. Then, you can instantiate as many scenarios as you want from any ScenarioConfig you created. You can run them, visualize the results, etc. of the various scenarios in the same application.

[FlorianJacta]

I am closing this issue as it is not a bug. However, if you have any remarks @Ginzou-3, you can create another issue to improve Taipy documentation or usability!