The mempool of a node is restricted in measurement (300MB by way of default). As soon as it is crammed and the node assists in keeping receiving transactions it’ll get started evicting some transactions. The transactions much less horny to miners are (intended to be) evicted to let room for higher-fee-paying transactions.
As pointed by way of @Murch in his personal solution, there was greater than 300MB of backlog around the community at many issues previously 3 months. Maximum of it paying greater than 1sat/vb. Your transaction should were evicted out of your node’s mempool (and possibly from the mempool of its friends as smartly).
Subsequently a sendrawtransaction of a kid (a transaction spending a few of its outputs) will fail, because the inputs of the kid would seem to be inexistent to the node. You will have to first rebroadcast the mother or father (the preliminary transaction), after which the kid, for it to be successful.
Notice you might be most effective in a position to do that as a result of your mempool is not actively purging transactions at 1sat/vb nowadays. In a different way you would need to post each your transactions as a unmarried package deal. This selection is not to be had but (as of October 2023).
