"Config has no key: driver-client-backend" error

Dear colleagues,

we are currently encountering the following error when running our MCH raw decoding workflow. This error seem to have appeared after an update of O2, and we have never seen it in the past:

[57608:internal-dpl-clock]: [10:30:54][STATE] Starting FairMQ state machine --> IDLE
[57610:internal-dpl-injected-dummy-sink]: [10:30:54][STATE] Exiting FairMQ state machine
[57610:internal-dpl-injected-dummy-sink]: [10:30:54][ERROR] Unhandled std::exception reached the top of main: Config has no key: driver-client-backend, device shutting down.
[57609:FileReader]: [10:30:54][STATE] Starting FairMQ state machine --> IDLE
[57608:internal-dpl-clock]: [10:30:54][STATE] Exiting FairMQ state machine
[57608:internal-dpl-clock]: [10:30:54][ERROR] Unhandled std::exception reached the top of main: Config has no key: driver-client-backend, device shutting down.
[57609:FileReader]: [10:30:54][STATE] Exiting FairMQ state machine
[57609:FileReader]: [10:30:54][ERROR] Unhandled std::exception reached the top of main: Config has no key: driver-client-backend, device shutting down.
[INFO] QUIT_REQUESTED

Do you have any idea where it could originate? We are not setting the driver-client-backend option anywhere, at least not explicitly…

Thanks!