# Harbor Trade Credit Series 2 Redemption Delays

**URL:** <https://gov.centrifuge.io/t/harbor-trade-credit-series-2-redemption-delays/4075>\
**Category:** Tinlake/ Centrifuge app\
**Created:** [May 20, 2022, 1:15pm UTC](https://gov.centrifuge.io/t/harbor-trade-credit-series-2-redemption-delays/4075 "2022-05-20T13:15:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![MuggleTown](https://avatars.discourse-cdn.com/v4/letter/m/54ee81/32.png) [@MuggleTown](https://gov.centrifuge.io/u/MuggleTown)\
**Post date:** [May 20, 2022, 1:15pm UTC](https://gov.centrifuge.io/t/harbor-trade-credit-series-2-redemption-delays/4075/1 "2022-05-20T13:15:32Z")

</div>

Harbor Trade Credit pools seem to have unusually long periods of wait between epoch close and the orders being executed. It has been stuck in the “ **Computing Orders** ” state for \>72 hours at Epoch 120. There is sufficient liquidity to execute all redemption orders as well.

The team has so far failed to provide a legitimate reason for the delay. Mostly getting a reply claiming there is 30 minutes remaining every time the query was posted on Discord or on email. Would like to get some clarity on how the epoch close works and what happens in between.

Will update here as and when I receive updates on status

---

<div class="post-metadata">

**Author:** ![MuggleTown](https://avatars.discourse-cdn.com/v4/letter/m/54ee81/32.png) [@MuggleTown](https://gov.centrifuge.io/u/MuggleTown)\
**Post date:** [May 20, 2022, 2:56pm UTC](https://gov.centrifuge.io/t/harbor-trade-credit-series-2-redemption-delays/4075/2 "2022-05-20T14:56:59Z")

</div>

Solved. There was an issue with the compute process

---

<div class="post-metadata">

**Author:** ![devin](https://dub1.discourse-cdn.com/flex013/user_avatar/gov.centrifuge.io/devin/32/2155_2.png) [@devin](https://gov.centrifuge.io/u/devin)\
**Post date:** [May 20, 2022, 3:41pm UTC](https://gov.centrifuge.io/t/harbor-trade-credit-series-2-redemption-delays/4075/3 "2022-05-20T15:41:38Z")

</div>

Hey! Tinlake devs have indeed been aware of this since the issue began have addressed it and fixed Harbor’s computation process. They’ll keep an eye on it going forward.
