All Collections
Data Management
Troubleshooting "Data is Not What I Expected" in WebAutomation Extractors
Troubleshooting "Data is Not What I Expected" in WebAutomation Extractors
Arslan Bisharat avatar
Written by Arslan Bisharat
Updated over a week ago

Introduction

If you're using WebAutomation's data extraction tools and find that the extracted data is not what you expected, this guide will help you troubleshoot and resolve the issue.

Steps to Address Unexpected Data in WebAutomation Extractors

Follow these steps to troubleshoot and fix unexpected data results in your WebAutomation extractor:

Step 1: Review Your Extractor Configuration

First, double-check your extractor's configuration settings to ensure that you have properly specified the columns, selectors, and extraction rules. A misconfigured extractor may yield unexpected data results.

Step 2: Verify the Website Structure

Visit the target website and check if its structure has changed since you last configured your WebAutomation extractor. Changes in the website structure can lead to unexpected data if the extractor is not updated accordingly.

Step 3: Test Your Extractor

After making any necessary adjustments to the configuration settings or selectors, run a test extraction to verify if the issue has been resolved. If the data is still not what you expected, proceed to the next step.

Step 4: Create a Support Ticket with WebAutomation

If you've tried the troubleshooting steps above and are still experiencing unexpected data results, it's time to create a support ticket with WebAutomation. Provide a detailed description of the problem, including the website URL, your extractor settings, and any observations made while troubleshooting. This information will help the WebAutomation support team understand the issue and provide an appropriate solution.

Step 5: Implement the Solution

Once the WebAutomation support team provides a solution for resolving the unexpected data issue, follow their instructions to implement the changes in your data extraction setup. This may involve updating your extractor's configuration or using a customized solution provided by the WebAutomation team.

By following this troubleshooting guide, you should be able to identify and resolve the issue of unexpected data in your WebAutomation extractor. If you're unable to fix the problem on your own, creating a support ticket with WebAutomation will ensure that the issue is addressed promptly and professionally.

Did this answer your question?