When a TransactionDataRequest for detection of transactions involving a given ephemeral address is serviced, we need to ensure that the next check is properly scheduled. The two paths by which transaction data requests of this sort are marked as having been serviced is via decrypt_and_store_transaction (for detected transactions) or via notify_address_checked when no relevant transactions are found.
Once we switch to doing detection of transparent UTXOs via augmented CompactBlock scanning, we will still need TransactionDataRequest-based address checking to traverse the wallet's gap limit during wallet recovery, since out-of-order scanning will result in transactions with addresses beyond the end of the gap limit being missed.