coldstorage – Bitcoin Core lacking public key when producing PSBT transaction

I exploit Bitcoin Core for offline signing. I created a legacy watch-only pockets, imported a public key utilizing importpubkey, then referred to as rescanblockchain, then generated a psbt transaction textual content(psbt_tx_txt), and at last efficiently signed offline with my Bitcoin Core signing consumer.

Nevertheless, if I restart the Bitcoin Core watch-only consumer, the psbt_tx_txt fails:

After restarting Bitcoin Core watch-only consumer, and producing the identical psbt_tx_txt once more, analyzing it with analyzepsbt, it prompts lacking pubkey:

{
  "inputs": [
    {
      "has_utxo": true,
      "is_final": false,
      "next": "updater",
      "missing": {
        "pubkeys": [
          "a_public_key_id"
        ]
      }
    }
  ],
  "price": 0.00001100,
  "subsequent": "updater"
}

However after I question the handle data with getaddressinfo, the general public key’s precisely included in it:

{
  "handle": "bc1......",
  "scriptPubKey": "......",
  "ismine": false,
  "solvable": true,
  "desc": "wpkh(......)#l8qyd3u4",
  "iswatchonly": true,
  "isscript": false,
  "iswitness": true,
  "witness_version": 0,
  "witness_program": "......",
  "pubkey": "a_PUBLIC_KEY",
  "ischange": false,
  "timestamp": 1,
  "labels": [
    "......"
  ]
}

If I exploit the psbt_tx_txt to signal on the signing consumer, the bitcoin core consumer prompts: transaction is lacking some details about inputs.

Which means that each time I create an offline signed transaction, I must create a pockets, importpubkey,and rescanblockchain.

I believe the general public key ought to have the ability to be inserted into the psbt_tx_txt, subsequent time I can simply create the psbt, am I lacking one thing?