This is a two-part question on 1) Canister Output Message Queue Limits, and 2) IC Management Canister Throttling Limits First, some context. I recently ran into the “Canister trapped explicitly: could not perform self call” issue when trying to asynchronously and concurrently query the canister s…

[image] dsarlis: Based on the general limit on the queue to a canister as already mentioned by the others, you can have up to DEFAULT_QUEUE_CAPACITY messages from a single canister to the management canister. So, if you want to get the status of thousands of canisters in the same message executi…

@icme It’s not that different than if you wanted to hit some other canister with this load. The queues are between pairs of canisters as already mentioned earlier in the thread. This means that if you have N canisters trying to hit the management canister then you’ll have N queues on the management …

[image] roman-kashitsyn: If you see could not perform self call, your canister might perform nested self calls exhausting the message queue limit. You might be able to fix the issue by restructuring the code. Is the code public? @roman-kashitsyn with the REPL I linked here I can’t even get c…

And when running this REPL with 200 as an argument, the following error appears. Server returned an error: Code: 400 () Body: Specified ingress_expiry not within expected range: Minimum allowed expiry: 2022-10-21 15:32:10.019462710 UTC Maximum allowed expiry: 2022-10-21 15:37:40.019462710 UTC Provi…

It looks as if the agent signs the signature request for the state read (i.e. for polling the response) when it makes the call, and when the call takes a while (e.g. a loop around await) does not extend the expiry in the read request, and after a while it expires. TL;DR: possibly a bug in the agent …

Oh, that’s an interesting theory - I’ll see if I can reproduce this with a new test

When developing complex projects, a number of internal asynchronous functions may be refactored to achieve functional reusability. For example private func fun1() : async Nat{ await ledger.transfer(..) //cross-canister call //... }; private func fun2() : async Nat{ // ... aw…

There is a new solution: add the countAwaitingCalls() method inside the ExperimentalInternetComputer Module so that Canister can limit the entry of new requests.

[image] bitbruce: The problem is that when 100 users call the canister at the same time, the number of Output Message Queues may exceed the limit of 500, and some await calls may be trapped. In your original example, each call uses await, which means it will schedule an outgoing self call mes…

Canister Output Message Queue Limits, and IC Management Canister Throttling Limits

Developers

cryptoschindler October 24, 2022, 9:31am 14

Thanks Joachim! I can confirm that calling it from dfx indeed works. Tagging @anon74414410 because I think he’s the owner of the agent.

Awarded: ICDevs.org Bounty #39 - Async Flow - One Shot - Motoko - $6,000

Topic		Replies	Views
Consensus and inter-canister calls Developers	12	3212	October 29, 2020
Messaging guarantees Developers	38	2497	June 1, 2023
Awarded: ICDevs.org Bounty #39 - Async Flow - One Shot - Motoko - $6,000 Bounties & RFPs	36	2221	March 8, 2023
Can some one do a YouTube video on optimizing cross canister calls? Developers	3	568	February 2, 2023
Error: The Replica returned an error: code 5, message: "Canister trapped explicitly: could not perform self call" Developers	8	2403	August 25, 2022

Canister Output Message Queue Limits, and IC Management Canister Throttling Limits

Related topics