An operation fails with opTOO_MANY_SUBENTRIES on mainnet
The account already has the maximum 1000 subentries: the operation fails at the operation level with opTOO_MANY_SUBENTRIES, not an op-specific code.
The shape
The account already has the maximum 1000 subentries: the operation fails at the operation level with opTOO_MANY_SUBENTRIES, not an op-specific code.
Variants
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p29-mainnet-mined-l65506631 | P29 | mainnet passphrase | mined from history | 2,053,600 B | 87a200665048… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| The result is txFAILED with opTOO_MANY_SUBENTRIES. | op_too_many_subentries | snapshotcorewalker |
Check it yourself
make verify # schema, hashes, the byte-for-byte round trip and every fact above
make oracle # the facts' values, re-read by stellar-core and the schema walkerEntry id failure.op.too-many-subentries-mainnet · compiled from catalog/failure.op.too-many-subentries-mainnet.json · entry.json
MANAGE_SELL_OFFER fails with MANAGE_SELL_OFFER_UNDERFUNDED
A transaction whose MANAGE_SELL_OFFER operation fails at apply is still written into the closed ledger: its fee is charged, its sequence number is consumed, and none of its operations change state.
PATH_PAYMENT_STRICT_RECEIVE fails with PATH_PAYMENT_STRICT_RECEIVE_NO_DESTINATION
A transaction whose PATH_PAYMENT_STRICT_RECEIVE operation fails at apply is still written into the closed ledger: its fee is charged, its sequence number is consumed, and none of its operations change state.