# Is it possible to attach (long running) business logic in the long running SuperNode process? 

**URL:** <https://discuss.flower.ai/t/is-it-possible-to-attach-long-running-business-logic-in-the-long-running-supernode-process/913>\
**Category:** General\
**Created:** [April 6, 2025, 8:52am UTC](https://discuss.flower.ai/t/is-it-possible-to-attach-long-running-business-logic-in-the-long-running-supernode-process/913 "2025-04-06T08:52:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![boscojacinto](https://dub1.discourse-cdn.com/flex013/user_avatar/discuss.flower.ai/boscojacinto/32/198_2.png) [@boscojacinto](https://discuss.flower.ai/u/boscojacinto)\
**Post date:** [April 6, 2025, 8:52am UTC](https://discuss.flower.ai/t/is-it-possible-to-attach-long-running-business-logic-in-the-long-running-supernode-process/913/1 "2025-04-06T08:52:45Z")

</div>

I understand that there is ClientApp short lived process that get triggered on an FL round, but was wondering if my application has some long running business logic how do I incorporate it within a client?

1. In case i chose to have the business logic as a separate process how can I spawn it when the supernode is created? Can it be spawned from inside the SuperNode?
2. Is there another alternative?

Regards,  
Bosco Jacinto

---

<div class="post-metadata">

**Author:** ![javier](https://dub1.discourse-cdn.com/flex013/user_avatar/discuss.flower.ai/javier/32/116_2.png) [@javier](https://discuss.flower.ai/u/javier)\
**Post date:** [April 18, 2025, 9:48am UTC](https://discuss.flower.ai/t/is-it-possible-to-attach-long-running-business-logic-in-the-long-running-supernode-process/913/2 "2025-04-18T09:48:34Z")

</div>

Hello @boscojacinto , interesting use case ! It sounds like what you need is to run the `SuperNode` with `--isolation=process`. In this way, it won’t automatically spawn a process to run the `ClientApp`. Instead, you need to launch it manually in a node in your same network. Like this:

```shell
flwr-clientapp --insecure --clientappio-api-address <supernode-address>:9094

```

Note the `--insecure` flag, this means that TLS isn’t enabled. This process is designed to be executed in the same machine or same network as your `SuperNode` (i.e. not through the open internet).

THe `flwr-clientapp` process is long running. Currently it doesn’t have built-in mechanisms to customize it. But it should be straightforward to do so if you are confortable forking the Flower repository. The `flwr-clientapp` is defined here: [flower/framework/py/flwr/client/clientapp/app.py at main · adap/flower · GitHub](https://github.com/adap/flower/blob/main/framework/py/flwr/client/clientapp/app.py) with the main infinite loop being defined in the `run_clientapp()` function.