bitcoin core – gettransaction RPC name doesn’t embrace all stability modifications

I’m battling unusual conduct of Bitcoin Core JSON-RPC name gettransaction. AFAIK, .particulars array of returned JSON ought to embrace all stability modifications. If I ship some quantity to myself (retrieved with getnewaddress), it ought to embrace each ship and obtain parts with the identical destructive and constructive quantity respectively.

This conduct is described e.g. in github challenge #4807 and I can verify that it is a truth in some circumstances.

Hovewer, I seen a special conduct typically. The .particulars array doesn’t embrace neither ship nor obtain parts.

Instance:

$ bitcoin-cli gettransaction XXX
{
  "quantity": -0.1,
  "payment": -0.00002,
  "confirmations": 7967,
  "txid": "XXX",
  ...,
  "particulars": [
    {
      "address": "SOME_RECIPIENT",
      "category": "send",
      "amount": -0.1,
      "vout": 0,
      "fee": -0.00002,
      "abandoned": false
    }
  ],
  "hex": "..."
}

The transaction in mempool.house or different blockchain explorers exhibits different outputs as effectively.

[
  {
    "value": 0.1,
    "n": 0,
    "address": "SOME_RECIPIENT",
    ...
  },
  {
    "value": 0.05,
    "n": 0,
    "address": "MY_ANOTHER_ADDRESS_1",
    ...
  },
  {
    "value": 0.04,
    "n": 0,
    "address": "MY_ANOTHER_ADDRESS_2",
    ...
  }
]

This transaction was constructed with sendmany RPC name.

Uncooked transaction in .hex factor consists of these in fact however they’re lacking within the .particulars factor.

Please word that each MY_ANOTHER_ADDRESS_n is tracked as .mine == true after I name getaddressinfo MY_ANOTHER_ADDRESS_n.

Does anybody has an concept why there are not any “stability modifications” within the .particulars array?