# Unreachable collections that present in blocks

**URL:** https://forum.flow.com/t/unreachable-collections-that-present-in-blocks/1083
**Category:** Flow Go SDK
**Tags:** flow-sdk-go
**Created:** [February 28, 2021, 3:26am UTC](https://forum.flow.com/t/unreachable-collections-that-present-in-blocks/1083 "2021-02-28T03:26:03Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![yondercode](https://avatars.discourse-cdn.com/v4/letter/y/e9a140/32.png) [@yondercode](https://forum.flow.com/u/yondercode)
#### Post date: [February 28, 2021, 3:26am UTC](https://forum.flow.com/t/unreachable-collections-that-present-in-blocks/1083/1 "2021-02-28T03:26:03Z")

</div>

Recently there seems to be some cases where a collection is present in a block’s `CollectionGuarantees` but the collection is not accessible through `GetCollection`

So far I have encountered with this issue several times:

```auto
height collection_hash
12000191 c5f4b105bddf47574c443b0fd971ba285d1cae88d2d59549a7aef3d0f7b789d1 
12023468 d33ff89b94f924052ec52ba17932e4fd4b8765df00acd681beab3ec8df5f3554 
12214718 fe2e49fa179df8c2952e1346f897caa6dbca0ca9e7d7c7e3c4ad7f499cc4ade0
12310920 4272858b1d76442d4fb7535b88999ccbc0c66b19e7cb922e2ff5ddab85fbbca2 
12367718 fa50a23d1e0b8c9357d938d47f602d22cfb0f7f869027c320ddc8fe8c2c32e26
12368306 988eb2bd30e8da1a0909c84c3c23883aad247cf801823aeb1e6a52434a5b2ba2
12353699 e35e88169f4cdcd68f76b32652ba08ba088df3ba67d9296adb864034f9e9b31a
12369551 e35e88169f4cdcd68f76b32652ba08ba088df3ba67d9296adb864034f9e9b31a
12371537 f9fee112c1d019f6b0babb62914afa06c643cef957af58d22e538fe78e02a353
12380977 937065a0f77c639b8412d89a8e82e91d82cd4bfd492f0aa56cda278b6220eb24
12381861 0cf762f358866b44fad9b79bc8ab31d5367b9ba82b3b8092a17e99719ecebece
12384326 63c9a04839783bc03e46b08d06d83a1693552edf4cfbcf95ce61e303b52a8661
12386060 fd406463a6316e78ae749bd49482c19506858672f4a76c9dc6298afd5a4944ed
12394217 d7da06b1cf42f83953151c5fb91ec465f766a048aa3b1e17ac1f283e223967d0
12394313 393cd784c9b3b148ebfd049a26384e86269e00c43de01917406731ce2fb9ab96
12394326 b27c1843f3e27226d57d704996b6cfc4de0618b5f850cf65c2c96b91f6770d68
12395314 c591caa69283aec9257a8a6fa24a3756dc2fd8670d1aa1a93f06318da00a5296
12395351 2e1036fe5843afb0d641f02bf825e3c485b791a252c2fa1c117d63dd84e3d258
12395955 9de2b5f071ac556159624dd7c1c5d5004541facfb2888a260d0911e7290cd1c7
12396350 7b3ba94992615cff99005256fb86e9b7273c5c13e063e5f1c8a3f266ba136a05
12396839 c97e1ac82848925ef0d53fc2f6d3cdd613e832c4452970cd38936559cc0c1b61
12396861 86f6c81e103bcff7331efa1c15bd52afa5447faf4675c21970828c6224bc4f41
12397029 eca3a22702c566d9010b7502edcbccce168c99f2258450cb130ce656fa6cd474
12397031 e25e36cf1bbdbb838d4d2ced74c98288880d122d31d68f42977153bdfa9c4707

```

There might be some more issues like this that I forgot to note, but this issue never happens before the first one at `12000191`.  
It would be nice if these cases can be investigated and fixed to get full data of the blockchain. Thank you!

---

<div class="post-metadata">

### Author: ![tadas\_z](https://avatars.discourse-cdn.com/v4/letter/t/a183cd/32.png) [@tadas\_z](https://forum.flow.com/u/tadas_z)
#### Post date: [March 1, 2021, 8:01am UTC](https://forum.flow.com/t/unreachable-collections-that-present-in-blocks/1083/2 "2021-03-01T08:01:00Z")

</div>

I can confirm that I’m having same issues with those collections.  
Today I discovered one more inaccessible collection  
Height: 12353699  
Collectioh hash: e35e88169f4cdcd68f76b32652ba08ba088df3ba67d9296adb864034f9e9b31a

---

<div class="post-metadata">

### Author: ![yondercode](https://avatars.discourse-cdn.com/v4/letter/y/e9a140/32.png) [@yondercode](https://forum.flow.com/u/yondercode)
#### Post date: [March 2, 2021, 2:46am UTC](https://forum.flow.com/t/unreachable-collections-that-present-in-blocks/1083/3 "2021-03-02T02:46:35Z")

</div>

More inaccessible collections today:

```auto
12369551 e35e88169f4cdcd68f76b32652ba08ba088df3ba67d9296adb864034f9e9b31a
12371537 f9fee112c1d019f6b0babb62914afa06c643cef957af58d22e538fe78e02a353
12378133 1f8a8610803848a9706f6af6ef0dd7fe67637d748396d1cab00d7c0d466e8488

```

---

<div class="post-metadata">

### Author: ![pete](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.flow.com/pete/32/191_2.png) [@pete](https://forum.flow.com/u/pete)
#### Post date: [March 2, 2021, 4:42am UTC](https://forum.flow.com/t/unreachable-collections-that-present-in-blocks/1083/4 "2021-03-02T04:42:45Z")

</div>

Thanks for reporting this, @yondercode and @tadas_z. We’re looking into it, and I’ll post here once we know more!

---

<div class="post-metadata">

### Author: ![pete](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.flow.com/pete/32/191_2.png) [@pete](https://forum.flow.com/u/pete)
#### Post date: [March 2, 2021, 5:10am UTC](https://forum.flow.com/t/unreachable-collections-that-present-in-blocks/1083/5 "2021-03-02T05:10:05Z")

</div>

I checked with the protocol team; it turns out this is a known issue, and they’re actively working on a fix.

---

<div class="post-metadata">

### Author: ![yondercode](https://avatars.discourse-cdn.com/v4/letter/y/e9a140/32.png) [@yondercode](https://forum.flow.com/u/yondercode)
#### Post date: [March 3, 2021, 9:20am UTC](https://forum.flow.com/t/unreachable-collections-that-present-in-blocks/1083/6 "2021-03-03T09:20:55Z")

</div>

Thank you for the update, @pete

I also find that some collections which are accessible have transactions which are inaccessible. Using the default access node on block 12409833 with the collections:

```auto
71288df225aea0763b542c9d20320a857e31032ddd803f209c851918ee1300e7
578c72a8f17d243d20f8460f8e58ffe33b0d52a16fe6c7aaf6d750e1a5b8243f
6ed8d95ed486118b4718483cc62a19caaf293303e17f18fc2b1281e5aa42b72d

```

Errors when getting the transactions that is contained in those collections:

```auto
client: rpc error: code = NotFound desc = no known transaction with ID 5ce083e59d6ff852a84277ca7ed54abd447140a36002f8dba09940e95d532aa3
client: rpc error: code = NotFound desc = no known transaction with ID 001f92185720032bafc508681532b17b87a3e1b693bd6c1c06ea8df6c7188094
client: rpc error: code = NotFound desc = no known transaction with ID 938510a8d6ed30d89adafdc8cc5985bb5da35bc9d965460b391f3f9f8777d5ce
...

```

These might be related with the original issue?

---

<div class="post-metadata">

### Author: ![pete](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.flow.com/pete/32/191_2.png) [@pete](https://forum.flow.com/u/pete)
#### Post date: [March 6, 2021, 3:33am UTC](https://forum.flow.com/t/unreachable-collections-that-present-in-blocks/1083/7 "2021-03-06T03:33:43Z")

</div>

Thank you for the information @yondercode and @tadas_z! This helped us find a solution.

We’ve identified the root cause and are preparing a patch for release!

---

<div class="post-metadata">

### Author: ![tadas\_z](https://avatars.discourse-cdn.com/v4/letter/t/a183cd/32.png) [@tadas\_z](https://forum.flow.com/u/tadas_z)
#### Post date: [March 15, 2021, 3:07pm UTC](https://forum.flow.com/t/unreachable-collections-that-present-in-blocks/1083/8 "2021-03-15T15:07:41Z")

</div>

@pete I can see that all collections are now accessible except this one:  
12000191 c5f4b105bddf47574c443b0fd971ba285d1cae88d2d59549a7aef3d0f7b789d1

Maybe because this node is still not patched with a fix? [access-001.mainnet4.nodes.onflow.org:9000](http://access-001.mainnet4.nodes.onflow.org:9000)
