# Request for Feedback on Governance: list\_neurons pagination API

**URL:** <https://forum.dfinity.org/t/request-for-feedback-on-governance-list-neurons-pagination-api/40362>\
**Category:** Developers\
**Tags:** nns\
**Created:** [January 21, 2025, 9:41pm UTC](https://forum.dfinity.org/t/request-for-feedback-on-governance-list-neurons-pagination-api/40362 "2025-01-21T21:41:21Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![jasonzhu](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jasonzhu/32/12251_2.png) [@jasonzhu](https://forum.dfinity.org/u/jasonzhu)\
**Post date:** [January 25, 2025, 12:30am UTC](https://forum.dfinity.org/t/request-for-feedback-on-governance-list-neurons-pagination-api/40362/21 "2025-01-25T00:30:55Z")

</div>

Thanks for the clarification! I did mean the ordering of response delivery compared to when the responses are produced, not when the requests are received. It’s good to know that the ordering isn’t guaranteed. In practice, is there any such scenario except for subnet splitting?

---

<div class="post-metadata">

**Author:** ![jasonzhu](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jasonzhu/32/12251_2.png) [@jasonzhu](https://forum.dfinity.org/u/jasonzhu)\
**Post date:** [January 25, 2025, 12:50am UTC](https://forum.dfinity.org/t/request-for-feedback-on-governance-list-neurons-pagination-api/40362/22 "2025-01-25T00:50:21Z")

</div>

Thanks. Good to know that we are on the same page.

IMHO, there can be other ways to recover from an unresponsive NNS Governance. For example, you can save the neuron ids from the responses, while having a recon task (running much less frequently) to look for neuron ids that you don’t know about. This way the cost is minimized most of the time, while being able to recover from extreme conditions. Of course, this is assuming listing neurons by subaccounts is not available yet.

---

<div class="post-metadata">

**Author:** ![free](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/free/32/615_2.png) [@free](https://forum.dfinity.org/u/free)\
**Post date:** [January 25, 2025, 7:50am UTC](https://forum.dfinity.org/t/request-for-feedback-on-governance-list-neurons-pagination-api/40362/23 "2025-01-25T07:50:12Z")

</div>

> [@jasonzhu](#):
>
> In practice, is there any such scenario except for subnet splitting?

I don’t think so. But I wouldn’t rely on that always being the case. The protocol specification (implicitly) allows the implementation to reorder responses in any way it wants (e.g. for efficiency or fairness purposes). So we may well end up doing that at some point.

---

<div class="post-metadata">

**Author:** ![dfxjesse](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/dfxjesse/32/17424_2.png) [@dfxjesse](https://forum.dfinity.org/u/dfxjesse)\
**Post date:** [January 25, 2025, 12:21pm UTC](https://forum.dfinity.org/t/request-for-feedback-on-governance-list-neurons-pagination-api/40362/24 "2025-01-25T12:21:17Z")

</div>

> [@jasonzhu](#):
>
> Of course, this is assuming listing neurons by subaccounts is not available yet.

Does this mean it might be coming 😉

---

<div class="post-metadata">

**Author:** ![icme](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/icme/32/4327_2.png) [@icme](https://forum.dfinity.org/u/icme)\
**Post date:** [January 26, 2025, 9:30pm UTC](https://forum.dfinity.org/t/request-for-feedback-on-governance-list-neurons-pagination-api/40362/25 "2025-01-26T21:30:33Z")

</div>

> [@jasonzhu](#):
>
> currently IC is still using the guaranteed response messaging model - when a canister makes an inter-canister call, it will wait for the response forever, until it hears back from the callee.

What about these cases where a request could fail to be delivered. Do any of these apply to your situation @dfxjesse? 👇

Simply wrapping all asynchronous calls in try/catch should cover request failures.

> [@Messaging guarantees](https://forum.dfinity.org/t/messaging-guarantees/17154/5):
>
> Thanks a lot for your posts. We hope to be able to clarify all the questions above – in particular why the introduction of timeouts is not a breaking change – with the explanation below. Also, thanks a lot for your suggestions on next steps to discuss. We like the suggestions but would propose to discuss them in separate threads. Canister messaging guarantees The IC protocol provides two guarantees for canister-to-canister messages: Request ordering: Successfully delivered requests are receiv…

[Previous page](https://forum.dfinity.org/t/request-for-feedback-on-governance-list-neurons-pagination-api/40362.md?page=1)