# \[BUG REPORT\] Deployment progress is reported at 69% while download haven't even started

**URL:** <https://hub.mender.io/t/bug-report-deployment-progress-is-reported-at-69-while-download-havent-even-started/1638>\
**Category:** General Discussions\
**Tags:** network\
**Created:** [March 12, 2020, 4:44pm UTC](https://hub.mender.io/t/bug-report-deployment-progress-is-reported-at-69-while-download-havent-even-started/1638 "2020-03-12T16:44:37Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![tranchitella](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/tranchitella/32/606_2.png) [@tranchitella](https://hub.mender.io/u/tranchitella)\
**Post date:** [April 1, 2020, 2:44pm UTC](https://hub.mender.io/t/bug-report-deployment-progress-is-reported-at-69-while-download-havent-even-started/1638/7 "2020-04-01T14:44:17Z")

</div>

@mzedel @ster with the current implementation, the “started\_at” field of the device deployment is to be intended as the date/time when the (whole) deployment has been created. This is going to change with the implementation of dynamic deployments, because the device deployment (the object that is device specific for a given deployment) will be dynamically created when the device asks for the update, not when the deployment is created by the user.

---

_[View the full topic](https://hub.mender.io/t/bug-report-deployment-progress-is-reported-at-69-while-download-havent-even-started/1638)._
