runehook indexing services stops after catching up to the latest block.

[phill-beyond]

Describe the bug
runehook indexing services stops after catching up to the latest block. Need to restart the process to start the indexing again.

To Reproduce
Steps to reproduce the behavior:
1, start process:
$ runehook service start --config-path Runehook.toml
...
Dec 24 21:02:07.618 INFO Edict DOG•GO•TO•THE•MOON 2399060302 tx: 0xf8216655b88a409d9927eb72a164ae55623d0e8de9202261a5e3ca52fd5e7424 (3627) @876206
Dec 24 21:02:07.633 INFO Flushing DB cache...
Dec 24 21:02:07.633 DEBG Flushing 5 supply changes
Dec 24 21:02:07.810 DEBG Flushing 22 ledger entries
Dec 24 21:02:07.812 DEBG Flushing 9 balance increases
Dec 24 21:02:08.060 DEBG Flushing 8 balance deductions
Dec 24 21:02:08.264 INFO Block 876206 indexed in 15.12s
Dec 24 21:02:08.286 INFO 1 blocks scanned, 1 actions triggered
Dec 24 21:02:08.291 INFO Caught up to bitcoind chain tip at 876206
Dec 24 21:02:08.293 INFO Listening for new blocks via Chainhook SDK
Dec 24 21:02:08.297 INFO Connecting to postgres at localhost:5432

2, After the process caught up to 876206 the indexing stopped. And I see the current block height reached 876,214 already.
I need to kill the process and start the process again to catch up to the newest block.

Expected behavior
I expect the runehook service can listen to the newest block and keep the indexing process going.