# Trigger same deployment with APIs

**URL:** <https://hub.mender.io/t/trigger-same-deployment-with-apis/7519>\
**Category:** General Discussions\
**Tags:** mender-client, management-api\
**Created:** [February 4, 2025, 12:46pm UTC](https://hub.mender.io/t/trigger-same-deployment-with-apis/7519 "2025-02-04T12:46:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vimoxshah](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/vimoxshah/32/2406_2.png) [@vimoxshah](https://hub.mender.io/u/vimoxshah)\
**Post date:** [February 4, 2025, 12:46pm UTC](https://hub.mender.io/t/trigger-same-deployment-with-apis/7519/1 "2025-02-04T12:46:16Z")

</div>

How can I retrigger the same deployment multiple times without encountering the “Artifact already installed” message?

Is there an API-based solution for this? One approach is to create two artifact versions and trigger two separate deployment APIs, ensuring that one always works. However, is there a more efficient way to handle this via API integration?

---

<div class="post-metadata">

**Author:** ![nickanderson](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/nickanderson/32/2257_2.png) [@nickanderson](https://hub.mender.io/u/nickanderson)\
**Post date:** [February 5, 2025, 1:54am UTC](https://hub.mender.io/t/trigger-same-deployment-with-apis/7519/2 "2025-02-05T01:54:55Z")

</div>

Hi @vimoxshah,

As I understand you don’t re-trigger a deployment. But you could create a new deployment and force installation of the artifact.

The [documentation for deployments says](https://docs.mender.io/overview/deployment)

> - A device won’t take part in the same Deployment twice
> - This can be overridden with the “Force update” option

I’m not sure that is well worded. Looking at the [API documentation for deployments](https://docs.mender.io/api/#management-api-deployments) briefly  
I find you can [list](https://docs.mender.io/api/#management-api-deployments-list-deployments), [create](https://docs.mender.io/api/#management-api-deployments-create-deployment) and [abort deployments](https://docs.mender.io/api/#management-api-deployments-abort-deployment).

The [NewDeployment](https://docs.mender.io/api/#management-api-deployments-schemas-newdeployment) and [NewDeploymenForGroup](https://docs.mender.io/api/#management-api-deployments-schemas-newdeploymentforgroup)  
has a `force_installation` property which is false by default but when enabled forces the installation of the Artifact disabling the `already-installed` check. So, I suspect that rather than force update allowing a device to take part in the same deployment it means the check if the artifact is already installed will be skipped so artifact installation will be done again.