# User stuck on early block

**URL:** <https://forum.autonomys.xyz/t/user-stuck-on-early-block/366>\
**Category:** Support\
**Tags:** desktop-app\
**Created:** [June 15, 2022, 4:41pm UTC](https://forum.autonomys.xyz/t/user-stuck-on-early-block/366 "2022-06-15T16:41:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ryan.yy.yeung](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/ryan.yy.yeung/32/326_2.png) [@ryan.yy.yeung](https://forum.autonomys.xyz/u/ryan.yy.yeung)\
**Post date:** [June 15, 2022, 4:41pm UTC](https://forum.autonomys.xyz/t/user-stuck-on-early-block/366/1 "2022-06-15T16:41:11Z")

</div>

Another user on Discord got confused by being synchronized on an early block on the desktop GUI. Is this normal?

 ![image](https://canada1.discourse-cdn.com/flex011/uploads/subspace/original/1X/6f1f35680be83007a52f6f57bd86a3cb0fd87703.jpeg)

---

<div class="post-metadata">

**Author:** ![ryan.yy.yeung](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/ryan.yy.yeung/32/326_2.png) [@ryan.yy.yeung](https://forum.autonomys.xyz/u/ryan.yy.yeung)\
**Post date:** [June 15, 2022, 4:45pm UTC](https://forum.autonomys.xyz/t/user-stuck-on-early-block/366/2 "2022-06-15T16:45:39Z")

</div>

@ImmaZoni @wei

I referred to this forum post, which basically says that its normal and that the Desktop GUI does not show the back-end, but the user has been stuck on this for over 24 hours with a lot of storage pledged, any thoughts?

> [@\[Gemini\] Farmer app stuck on early block](https://forum.autonomys.xyz/t/gemini-farmer-app-stuck-on-early-block/180/8):
>
> see the #announcements channel for an update with this issue.

---

<div class="post-metadata">

**Author:** ![ImmaZoni](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/immazoni/32/7_2.png) [@ImmaZoni](https://forum.autonomys.xyz/u/ImmaZoni)\
**Post date:** [June 15, 2022, 6:57pm UTC](https://forum.autonomys.xyz/t/user-stuck-on-early-block/366/3 "2022-06-15T18:57:17Z")

</div>

This is an issue because of how the logic works with checking to see if the status is complete. The logic is simply current node block # compared to the target # (as shown in the cli or logs of subspace desktop)

Now the issue likely occurs when the node is on a fork and the target may be the same (or even lower) than the nodes current block, so the logic thinks its fully synced and moves onto the next page. I would suggest the user pay attention to the logs as for latest syncing & node status until we get this resolved.

Reported the bug here [Application moves past `Syncing` screen before actually syncing. · Issue #264 · subspace/subspace-desktop · GitHub](https://github.com/subspace/subspace-desktop/issues/264)