I am completely mystified. I built a bot which I had been using for almost a year when it suddenly threw up the error message: Source Data has no columns or rows.
I built the bot to extract information from a webpage. I indicate the information I want manually and then run the bot. The text gets sent to a data table and then I use the Write Data table to excel instruction and usually it copies. Since I do this over a number of pages (all manually as the multiple page option doesn’t work for some reason), I append the information in the Excel sheet.
Since the error, I have rewritten the bot a number of times, but keep getting the same error and have no idea how to solve it. I have no coding training or previous experience and write the bots in a very basic way: Use Excel resource - use browser resources - table extraction - write data table to Excel.
I have looked up this error in the online forum, but haven’t found the topic where there is scraping from a website specifically. I would be most grateful for any suggestions.
This error means UiPath is no longer extracting any data from the webpage — your DataTable is empty. Excel is not the problem.
Website layout changed → Re-indicate the table from scratch Page not fully loaded → Add Check App State / Delay before extraction Variable mismatch → Make sure Extract Table and Write Range use the same DataTable
The error happens because the extracted DataTable is empty. The website likely changed and the table is no longer being captured. Re-indicate the table, ensure the page is fully loaded, and check that the Extract Table activity actually returns data before writing to Excel.
The error is not Excel related; it means data is not coming from the web page. You have to Re-validate the table extraction and a count check, if dt.rows.count>0 or if it is not empty before writing to Excel.
This error means the web table extraction is returning an empty DT, which usually happens when the webpage layout changed, the selector no longer matches, or the extraction scope is pointing to the wrong element. fix it by re‑indicating the table, validating selectors in UiExplorer, confirming the page fully loads before extraction, and adding a short delay or “Check App State” before the Extract Table activity.
If helpful, mark as solution. Happy automation with UiPath