Difference between revisions of "Error Handling inside Internet Computer"
From Internet Computer Wiki
| Line 6: | Line 6: | ||
===== MaxNumberOfCanistersReached: StatusCode 102 ===== | ===== MaxNumberOfCanistersReached: StatusCode 102 ===== | ||
| − | When | + | There is an option in the NNS registry to set a max limit on the number of canisters in a subnet. When a new canister is created, the subnet checks if this maximum limit is reached and throws an error accordingly. Currently, we don’t limit the number of canisters in a subnet. |
===== CanisterOutputQueueFull: StatusCode 201 ===== | ===== CanisterOutputQueueFull: StatusCode 201 ===== | ||
Revision as of 19:47, 24 October 2022
This Page is Still Work in Progress
SubnetOverSubscribed: StatusCode 101
This error is raised when installing a new canister or increasing memory allocation in the canister, and no compute allocation or memory capacity is left in the subnet.
MaxNumberOfCanistersReached: StatusCode 102
There is an option in the NNS registry to set a max limit on the number of canisters in a subnet. When a new canister is created, the subnet checks if this maximum limit is reached and throws an error accordingly. Currently, we don’t limit the number of canisters in a subnet.
CanisterOutputQueueFull: StatusCode 201
This is for inter-canister calls. You will see this if your canister is seeing a lot of outgoing calls. It may be around 500 messages per queue. There is a separate queue for each canister.
IngressMessageTimeout: StatusCode 202
Timeout is 5 minutes. This can happen if the system is quite loaded.