# Fleet Pipeline does not exist - Data Streams not getting data **URL:** \ **Category:** Elasticsearch\ **Tags:** fleet\ **Created:** [October 5, 2021, 5:16am UTC](https://discuss.elastic.co/t/fleet-pipeline-does-not-exist-data-streams-not-getting-data/285877 "2021-10-05T05:16:14Z")\ **Posts on this page:** 1\ **Showing post:** 14
**Author:** ![joshdover](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joshdover/32/42020_2.png) [@joshdover](https://discuss.elastic.co/u/joshdover)\ **Post date:** [October 20, 2021, 7:39am UTC](https://discuss.elastic.co/t/fleet-pipeline-does-not-exist-data-streams-not-getting-data/285877/14 "2021-10-20T07:39:20Z")
Hi all, thanks for being some of our first adopters of Fleet and Elastic Agent. It seems you all have encountered one of our rough spots in integration upgrades. This is definitely not the experience we want and is something we're planning to address in an upcoming release as part of [[Fleet] Handle common transient errors during package installs with a retry · Issue #111859 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/111859). In the meantime, there is an API workaround you can use to force these assets to be reinstalled without having to wipe everything and start over. This command will force the base package to be reinstalled: ```auto curl -XPOST \ --url http:///api/fleet/epm/packages/system-1.1.2 \ -u : \ -H 'content-type: application/json' \ -H 'kbn-xsrf: x' \ --data '{"force": true}' ``` You'll want to be sure you use the correct version number at the end of the URL (I used `1.1.2` here). You can see which version is currently installed by visiting `http:///app/integrations/detail/system/settings`. This can also be used for other packages as well, just change the `system` in the URL to another package name and use the correct version number. I hope this helps! --- _[View the full topic](https://discuss.elastic.co/t/fleet-pipeline-does-not-exist-data-streams-not-getting-data/285877)._