Execution mode no longer supported in v11

[Aristide]

Hello,

since v11 I get this message when I import a flow using the Execute command app :
Property "Execution mode" is no longer supported in
Execute command app from version 11. Default Execute mode is "Concurrent". Enable "Show advanced element properties" property in the flow properties pane, an extra property "Idle after job (secs)* will be available, which can be used for serialized processing.

OK this is clear, I understand. But do I have to modify something to make this message disappear permanently?
I don't have this app to update...

Even if i recreate a new flow, the message will come back when I import the flow...

I shouldn't have cared?

Thank you for the information

AF

[patej]

Yes, the message is annoying because we've understood it the first time it appeared, but to my knowledge there is nothing you can do before the message is removed from a new version of the app.

[Aristide]

Hello Patej,

Thanks for this confirmation, I'll stop looking

Have a nice day.

[rocky07]

You don’t need to worry too much about that message—it’s just an informational notice. Starting from version 11, the “Execution mode” property was removed, and all executions now run in “Concurrent” mode by default. If you’re not using any serialized or timing-based execution logic, you can safely ignore it. To stop seeing the warning, you’d need to remove the deprecated “Execution mode” property from your flow configuration before exporting or importing, but functionally, everything should still work fine without any manual changes.