Skip to content

Commit dd0c069

Browse files
feat: Add docs for two new execution errors related to canister_etadata
Added explanations for canister metadata errors. Related PRs: - dfinity/ic#6725 - #6069
1 parent dfd5322 commit dd0c069

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

docs/references/execution-errors.mdx

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -740,6 +740,25 @@ An example of this error is:
740740

741741
To fix this error, ensure that you are a controller of the canister that the snapshot belongs to.
742742

743+
### Canister metadata no wasm module
744+
745+
This indicates that you are trying to fetch the metdata of a canister while there is no Wasm module running on that canister.
746+
747+
An example of this error is:
748+
```
749+
The canister xxx-xxx has no Wasm module and hence no metadata is available.
750+
```
751+
752+
### Canister metadata section not found
753+
754+
This indicates that you are trying to fetch a metadata section that either does not exist, or that is private while you are not the controller of the canister.
755+
756+
An example of this error is:
757+
```
758+
The canister xxx-xxx has no metadata section with the name <metadata section name>.
759+
```
760+
761+
TO fix this error, make sure the metadata section exists for the given canister and section name. Or in the case of a private section, resend the message with a principal that is the controller of the canister.
743762

744763
[canbench]: /docs/building-apps/advanced/benchmarking
745764

0 commit comments

Comments
 (0)