Adding Processors / Pipelines to an integration attached to a policy breaks running agent (Error creating runner from config: Can only start an input when all related states are finished)

[mehdi-lamrani]

8.7 here,

Pretty self explanatory. Steps in the screenshots.

Error creating runner from config: Can only start an input when all related states are finished

What does related states mean ? there is only that single integration on that single policy attached to that single agent (to avoid any collusion)

My dirty fix is to unenroll and reenroll the agent. But that is really ugly and very unefficient. What's the correct way to update integrations processors and pipelines on an integration tied to a policy having a live running agent ?

Thanks in advance

[mehdi-lamrani]

Up ?
Did anyone experience this as well ?
This behavior is concerning, and does not inspire confidence to deploy it in production environment....