Difference between revisions of "Error Handling inside Internet Computer"
From Internet Computer Wiki
(Created page with "= This Page is Still Work in Progress =") |
|||
Line 1: | Line 1: | ||
= This Page is Still Work in Progress = | = This Page is Still Work in Progress = | ||
+ | |||
+ | |||
+ | * SubnetOverSubscribed: StatusCode 101 | ||
+ | This error is raised when no compute allocation or memory capacity is left in the subnet. This could be when installing a new canister or increase memory allocation in the canister. | ||
+ | |||
+ | * MaxNumberOfCanistersReached: StatusCode 102 | ||
+ | When the canister is first created. Currently, we don’t limit the number of canisters. But there is an option to set a max limit in the registry. | ||
+ | |||
+ | * 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. |
Revision as of 19:40, 24 October 2022
This Page is Still Work in Progress
- SubnetOverSubscribed: StatusCode 101
This error is raised when no compute allocation or memory capacity is left in the subnet. This could be when installing a new canister or increase memory allocation in the canister.
- MaxNumberOfCanistersReached: StatusCode 102
When the canister is first created. Currently, we don’t limit the number of canisters. But there is an option to set a max limit in the registry.
- 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.