Hey Drake, thanks for the message and for flagging this! I jumped into the table to check it out but seems like it already finished running. The provider's API rate limits might've been reached/capped at the time and thus was slower then usual but working overall.
Let me know if you see this happen again so we can check it out, thanks!