Hi Stefan, your concern is valid. Ideally, you don't want this QAction to block the entire workflow. We have a couple of strategies to address this, and the best approach depends on certain variables that I currently don't have. To maintain most of your existing logic, you could consider queueing your QAction, which would create a dedicated thread for it (https://docs.dataminer.services/develop/schemadoc/Protocol/Protocol.QActions.QAction-options.html#queued). However, we need to be cautious with this approach, as we must manage its lifecycle and ensure it ends or restarts when the element is stopped or restarted. We also need to be careful with accessing shared memory and make sure that not RTEs will be generated. An alternative might be to use a serial interface to receive asynchronous data and then trigger a QAction whenever data is received to correctly process it.