Difference between revisions of "Error Handling inside Internet Computer"
Line 13: | Line 13: | ||
===== IngressMessageTimeout: StatusCode 202 ===== | ===== IngressMessageTimeout: StatusCode 202 ===== | ||
A user can call a method of a canister by sending an ingress message. The ingress messages go through consensus protocol. The ingress messages that are accepted by the consensus layer are pushed into ingress queue of the corresponding canister. The canister processes the messages in its ingress queue in order. If the system is quite loaded and if a message stays in the ingress queue for over 5 minutes, then IngressMessageTimeout error is thrown. | A user can call a method of a canister by sending an ingress message. The ingress messages go through consensus protocol. The ingress messages that are accepted by the consensus layer are pushed into ingress queue of the corresponding canister. The canister processes the messages in its ingress queue in order. If the system is quite loaded and if a message stays in the ingress queue for over 5 minutes, then IngressMessageTimeout error is thrown. | ||
+ | |||
+ | ===== CanisterNotFound: StatusCode 301 ===== | ||
+ | |||
+ | ===== CanisterMethodNotFound: StatusCode 302 ===== | ||
+ | |||
+ | ===== CanisterAlreadyInstalled: StatusCode 303 ===== | ||
+ | |||
+ | ===== CanisterWasmModuleNotFound: StatusCode 304 ===== | ||
+ | |||
+ | ===== CanisterEmpty: StatusCode 305 ===== |
Revision as of 20:48, 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
Internet Computer allows one canister to call another canister. These outgoing inter-canister canister calls are placed in the output queues of the canister. There is a currently a limit of 500 messages per output queue. CanisterOutputQueueFull error is thrown when this limit is reached.
IngressMessageTimeout: StatusCode 202
A user can call a method of a canister by sending an ingress message. The ingress messages go through consensus protocol. The ingress messages that are accepted by the consensus layer are pushed into ingress queue of the corresponding canister. The canister processes the messages in its ingress queue in order. If the system is quite loaded and if a message stays in the ingress queue for over 5 minutes, then IngressMessageTimeout error is thrown.