You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It comes from that perspective when we are hit by the cache. The user will see a timeout instead, but in reality, we have no data and no timeout error at all.
So even being a "expected" behavior, for the user perspective it is an error/failure.
Today, when any error happens in the crawler the listener (webhook) is not being triggered.
This should be fixed, and the failed handler should be implemented in the listener as well (cloud)
The text was updated successfully, but these errors were encountered: