This article explains steps you can take to investigate issues with tasks that have a method of Scraper.

Investigating Scraper QA Issues

If we have zero or low leads or sales counts:

1. Check Slack channel #wall-e_alerts for any alerts for the current dealer.
   1. See Wall-E Troubleshooting Issues
2. Verify the login still works.
   1. If a password change is required, make sure to update the Wall-E dealer profile in the Wall-E Onboarding Site.
3. Verify we still have the correct permissions to pull the data (try to manually pull it and see what you come up with).  If we have permissions but no/little data comes up, the dealer has likely changed vendors.  Tag the CSL and CS Support Team to notify them of the issue and request they ask the dealer if they have switched vendors.
4. Verify the store setup is still the same in the CRM (stores have not changed names)
   1. If needed, you may need to update the Wall-E dealer profile in the Wall-E Onboarding Site.
5. If data appears correct in the CRM but not in Looker, check property alias mappings.  See:
   1. Mapping Leads Files
   2. Mapping Sales Files 
   3. Mapping Multi Files 
6. You can check the data that is being downloaded by Wall-E by looking in the Wall-E Archive in Google Cloud Stroage.
   1. If data appears in the CRM but there are no files for the dealer in the archive cloud storage, the steps to pull the data may have changed in the CRM and Wall-E needs a code update.  In this case, open a ticket for the Nix team to update Wall-E code on the Tickets Board.