I was running a simple scrape a list, with pagination, add to google sheet - workflow.
It seemed to run there all of the pages but then threw up the error at the end. I’ve tried reducing the number of items scrapped. (btw, the scrapper doesn’t listen to that. If I put ‘50’ in the selection, it ends up going through all 2000)
{
"clientErrorCode":An unhandled error occurred. The engineering team was notified and will investigate the reason. If it is blocking you, please feel free to file a bug report at https://www.bardeen.ai/bug-report
....
How to get Bardeen error messages?
Bardeen usually provides error messages. These help us solve the issue faster. You can check them by:
Opening Bardeen extension
On the right top corner, next to your profile image👤, you’ll find an icon for history: . Click it.
Then check the Errors tab. Copy the relevant bug to your case
(Ex: if you ran a salesforce automation, copy the salesforce issue).
Steps to reproduce this issue:
Please provide a detailed account of the steps taken to encounter the issue. Where did you start? What actions did you perform? Where did you encounter the error?
Ex: I pinned this salesforce automation to my app, connected salesforce and then ran it over this linkedin profile. I received the error message and have been unable to resolve it.
Bardeen version: ____
How to check the Bardeen version: right click on your Bardeen extension > Click on Manage Extension > Copy the extension version number.
After reviewing your issue in detail, we believe that it requires additional expertise for a resolution. Therefore, we have escalated your ticket to our higher-level support team. This team specializes in handling more complex issues and has the necessary resources to provide you with the best possible solution.
Please rest assured that we are committed to resolving your concern as swiftly and efficiently as possible. The advanced support team will review your case and contact you directly with further updates or if they need any additional information from you.
Your patience and understanding are greatly appreciated as we work to resolve your issue. In the meantime, if you have any more questions or additional information to provide, please feel free to reply to this email. We are here to help!
Cheers,
Lucy
Cheers!
Customer Support - bardeen.ai
Explore | @bardeenai | Bardeen Community
Can you please share the playbook with the scraper model that has the issue and the page URL you are running it?
I’ve tried reducing the number of items scrapped. (btw, the scrapper doesn’t listen to that. If I put ‘50’ in the selection, it ends up going through all 2000
Scraper can keep paginating if for some reason it scrapes single item from every page, maybe the container selector on followup pages didn’t work?
It seemed to run there all of the pages but then threw up the error at the end
Sorry for that, we are working on improving the situation with more meaningful error reporting, this can potentially happen if page load takes long time or last page doesn’t load? But it’s hard to tell without actual reproduction.
Looking forward to hearing back from you,
Cheers,
Manvel
Customer Support - bardeen.ai
Explore | @bardeenai | Bardeen Community
Stepping in to follow up for Manvel. Any chance you can share the page you are trying to scrape? It is cut off in the screen sharing and we would like to do some investigating on the website itself.
Thanks!,
Lucy
Customer Support - bardeen.ai
Explore | @bardeenai | Bardeen Community
Sorry for the late reply and thanks for sharing the screen recording.
Indeed I see that the scraper seem to fail during the redirection and it’s hard to tell what exactly went wrong without closer look into errors we might be hiding, we used to have few issues with the websites which were cleaning up some Bardeen logic on the redirection without firing proper redirection event, that has been fixed in the latest version. I will suggest to try updating Bardeen to the latest version and give it another try. Here is how to update Bardeen to the latest version:https://www.loom.com/share/862697b74a5f4502a6f39ab76d80d03f
If updating Bardeen doesn’t help, I will suggest to add a delay to the scraping command, Chrome has an issue with propagating errors we are working for working around that for upcoming releases, which potentially may cause Bardeen thinking that it’s ready to operate on the redirected page, but in reality it’s not ready and Chrome hides that information from us, setting delay on the scraping command will fix that: Here is how to add delay to the Scraping command:https://www.loom.com/share/99a526d1a1c948478e9d99d6e5bbf26f
surre thing. I just schedule something for April 1
Thanks for scheduling the call, I have switched it to 30m call, but we can go overtime if that will not be enough, looking forward to the call and I am sure we will figure out why Bardeen failed scraping the target page.
Meanwhile can you please share the playbook with me I would like to double check that scraper model itself doesn’t have some hints on what might went wrong. Here is how to share playbook:https://www.loom.com/share/f2457336392c433fb51308eba6bbfa3f
Please let me know if any of the solutions above fixed the issue.
Thanks in advance,
Manvel
Customer Support - bardeen.ai
Explore | @bardeenai | Bardeen Community
. Click it.
How to check the Bardeen version: right click on your Bardeen extension > Click on Manage Extension > Copy the extension version number.
Video recording or screenshots (optional, but recommended):
