# 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)

**URL:** <https://discuss.elastic.co/t/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/332909>\
**Category:** Elastic Agent\
**Created:** [May 9, 2023, 11:22am UTC](https://discuss.elastic.co/t/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/332909 "2023-05-09T11:22:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mehdi-lamrani](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mehdi-lamrani/32/108993_2.png) [@mehdi-lamrani](https://discuss.elastic.co/u/mehdi-lamrani)\
**Post date:** [May 9, 2023, 11:22am UTC](https://discuss.elastic.co/t/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/332909/1 "2023-05-09T11:22:07Z")

</div>

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

 ![Screenshot 2023-05-09 at 13.14.12](https://us1.discourse-cdn.com/elastic/original/3X/5/f/5f626e1c69690d4518d399eaa37aab9db3228561.png)

 ![Screenshot 2023-05-09 at 13.18.04](https://us1.discourse-cdn.com/elastic/original/3X/8/0/805cc61a7c5cf735267dc8935742d0fcf7fa1293.png)

 ![Screenshot 2023-05-09 at 12.51.17](https://us1.discourse-cdn.com/elastic/original/3X/7/4/74207c7673ccb73105cf283a5e19713ab300ed22.png)

---

<div class="post-metadata">

**Author:** ![mehdi-lamrani](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mehdi-lamrani/32/108993_2.png) [@mehdi-lamrani](https://discuss.elastic.co/u/mehdi-lamrani)\
**Post date:** [May 11, 2023, 12:14pm UTC](https://discuss.elastic.co/t/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/332909/2 "2023-05-11T12:14:52Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 8, 2023, 12:15pm UTC](https://discuss.elastic.co/t/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/332909/3 "2023-06-08T12:15:38Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.