Disable flows from running on a specific directus instance

Summary add the option to disable flows from running on a specific directus instance, maybe RUN_FLOWS=false Basic Example We have a bunch of flows that run based on different events, the problem is that these flows are expensive, which are causing the HTTP/API calls to slow down on directus. We would like to run different directus instances, one for serving HTTP/API/Web requests and another for running flows, just like Web-Worker Architecture. Motivation avoid flows from impacting the end user experience. Detailed Design ![image]( Requirements List flows run conditionally Drawbacks data sync/missmatch? Alternatives Using celery or sidekiq to process background jobs, however this is not ideal because it introduces a new tool that needs to be maintained Adoption Strategy This should not be a breaking change. By default RUN_FLOWS=true so it should work as it does nowadays. But if you set it to RUN_FLOWS=false, it will only enqueue jobs as events happen, so another dir…