# Project activity: Time calculation not correct when deleting entries

**URL:** <https://community.awork.com/t/project-activity-time-calculation-not-correct-when-deleting-entries/802>\
**Category:** Developer Forum\
**Created:** [17. März 2024 um 20:26 UTC](https://community.awork.com/t/project-activity-time-calculation-not-correct-when-deleting-entries/802 "2024-03-17T20:26:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![herzkerl](https://dub1.discourse-cdn.com/flex013/user_avatar/community.awork.com/herzkerl/32/1200_2.png) [@herzkerl](https://community.awork.com/u/herzkerl)\
**Post date:** [17. März 2024 um 20:26 UTC](https://community.awork.com/t/project-activity-time-calculation-not-correct-when-deleting-entries/802/1 "2024-03-17T20:26:03Z")

</div>

I used the API to migrate a few (800-ish) entries from a .csv file to awork. Due to a few mistakes I had to do that several times for some projects. In between, I batch deleted the time entries.

It seems the calculated time that’s shown in ‚project activity‘ doesn’t reflect that. In the posted screenshot you’ll see 95:04h, despite the sum of the entries is 47:32h. (In some projects, it’s more than twice the actual sum, because those entries were imported more than twice.)

I’m guessing the deletion of time entries does not trigger re-calculating this activity. Not sure if that should behave that way, just wanted to post this here to let you know.

![Bildschirmfoto 2024-03-17 um 21.19.22](https://europe1.discourse-cdn.com/flex013/uploads/awork1/original/1X/748ff77b7a9375841071737c8fa8d16bad3d600f.png)

---

<div class="post-metadata">

**Author:** ![Sebastian](https://dub1.discourse-cdn.com/flex013/user_avatar/community.awork.com/sebastian/32/89_2.png) [@Sebastian](https://community.awork.com/u/Sebastian)\
**Post date:** [11. April 2024 um 14:33 UTC](https://community.awork.com/t/project-activity-time-calculation-not-correct-when-deleting-entries/802/2 "2024-04-11T14:33:00Z")

</div>

Hi @herzkerl, thanks for reporting this. I’ll create a bug ticket internally so we can investigate this.
