Fridolín Pokorný

Verification of configuration issues the following warning: ```console > $ pipenv run selinon-cli inspect -n nodes.yaml -f flows.yaml 22096: [06:58:43] selinon.system _setup_nodes:1067: Unknown configuration keys in the nodes definitions, will...

> 4. When we trigger the flow execution from API/Function we get the trace which says Configuration is not loaded. The first thing that came to my mind when reading...

Selinon needs to register Selinon specific tasks (``Dispatcher`` and ``SelinonTaskEnvelope``) to Celery. Otherwise Celery does not have notion about these tasks. > But the flow and nodes are initialized dynamically...

> yes, we are creating flow dynamically and yes it is not available on the application startup. Then the error message you are seeing is correct. Selinon does not know...

> Not sure whether it is feasible? This will require larger code changes. I don't have currently time for that. But patches are always welcome.

Sure, I'm open to any enhancements.

Let me know if I can help you with anything. Just to give pointers - basically the patch would include configuration to be passed onto queue and accepted by the...

Hi Rathish, first of all thanks for diving into this that fast. Really nice observations and questions! > 1. We tried to pass the Config object between the Tasks (Dispatcher,...

> We want to handle the config cache via Mixin extension , in our case of implementation plan to cache it in database to handle repeated flow execution scenario. If...

> There are some initial success, but we are not able execute two different flows with different configuration in parallel. This could be somehow limitation of the design where a...