Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(crawler): fix failed webhook #80

Open
brunoocasali opened this issue Aug 22, 2023 · 2 comments
Open

fix(crawler): fix failed webhook #80

brunoocasali opened this issue Aug 22, 2023 · 2 comments

Comments

@brunoocasali
Copy link
Member

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)

@bidoubiwa
Copy link
Contributor

I think it does trigger a failure. Can you provide an example?

@brunoocasali
Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants