# Can't call an imported Actor's query functions

**URL:** <https://forum.dfinity.org/t/cant-call-an-imported-actors-query-functions/1732>\
**Category:** Developers\
**Created:** [January 7, 2021, 7:30am UTC](https://forum.dfinity.org/t/cant-call-an-imported-actors-query-functions/1732 "2021-01-07T07:30:13Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![enzo](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/enzo/32/268_2.png) [@enzo](https://forum.dfinity.org/u/enzo)\
**Post date:** [January 8, 2021, 6:57pm UTC](https://forum.dfinity.org/t/cant-call-an-imported-actors-query-functions/1732/8 "2021-01-08T18:57:18Z")

</div>

> [@mymikemiller](#):
>
> What’s the problem with XNet Transfer then?

Will have to get back to you on the specifics, but my strong suspicion here is that the implementation is not optimized. My guess would be that they don’t do any message introspection to distinguish between updates and queries (since every query can be run as an update), and that manifesting itself in this limitation. I will mention this to their PM and see what the turnaround time could be for a fix. Thanks for raising this.

---

_[View the full topic](https://forum.dfinity.org/t/cant-call-an-imported-actors-query-functions/1732)._