Hey there, thanks for reaching out! It looks like this issue has been resolved - all the rows in this table ran successfully for the HTTP column. This issue you were running into was likely related to a temporary performance issue due to the large amount of queries you were pushing to Serper through the HTTP enrichment. I hope this was helpful. If there's anything else I can assist you with, please let me know!