mysql Binlog collection is not in order

Question 1：

The configuration looks like this：

"database.include.list": "ais_asr_controller_prod",
"table.include.list": "ais_asr_controller_prod.asr_controller_log,ais_asr_controller_prod.wakeup_monitor",

There is a big event at 2:00 in the morning, and the captured two tables always have data, and data will be lost at 2:00 in the morning every day, and the order of binlog collection is also as shown above.
The data generation time was collected at 2022-12-30 02:00:23 first, then at 2022-12-30 02:00:00, and finally jumped back to 2022-12 -30 02:03:48

As shown in the figure below, there are two large binlog files

Question 2：

Pay attention to the following figure again. In the case of continuous collection, there is a situation where the binlog file is not collected, and mysql-bin.025443 is not collected.

There is a situation where the binlog file is not collected. May I ask what caused this? Is it because there is no data in these two tables in the binlog file?