Several months ago (noting while an earlier post stated a year, first confirmed mention is April) Binance reached out in a private chat group with Dogecoin Core developers and members of their Operations team that they had cases where transactions were stuck, meaning they were not being mined successfully. It was suggested Binance use RBF (replace by fee) on these transactions, which would replace the original transactions with a new transaction with a higher fee paid. Notably this was suggested because replace by fee invalidates the previous transaction (hence “replace”). As the transaction had RBF disabled, it was recommended to create a new transaction manually, which would consume the same inputs to forcibly invalidate the previous transaction.
Some time later Binance notified the group that they had account reconciliation issues. Multiple developers were unable to reproduce those issues with the data we were given by Binance, but it was suggested to use the -zapwallettxes command line option to mitigate the issue. This is notable as we believe this would have also prevented the issue seen.
Yesterday November 10th the group was notified that previously stuck transactions had suddenly relayed successfully, post 1.14.5 update; likely because minfees have been lowered in 1.14.5, making the previously valid but unrelayable transactions relayable. The sole example given by Binance, is a transaction with fees which are valid as of v1.14.5, but were invalid (too low) in 1.14.3 and before. Note, Binance updated directly from v1.14.3 to 1.14.5, in the past few days.