Common Task log Meaning

1. Getting Session - Getting session can be best explained as in the bot is currently linking the Proxy with the Footsite to Pick up the Sku Information. After getting session, the bot will proceed to change the PID to the name of the product you are trying to cop

2. Task in queue [503] - This can be best explained as the task is in a queue (virtual line) which Footsites make each task pass to then find the product and start adding to cart.

3. Retrying adding to cart - Adding to cart can be best explained as in the bot is currently trying to add the item you choose to cart so that it can checkout the item. If the bot is successful at adding the item to cart the task will say (sending billing)

4. Sending Billing - Sending Billing can be best explained as in the bot is currently typing/placing your profile item onto the sites checkout page. After sending billing the bot will proceed to checkout.

5. Checking out - Checking out can be best explained as in the bot is currently trying to checkout the item you wanted and your order is being processed. If your order goes through your checkout sound will play and the color of the writing (checking out) will turn green indication you have purchased the item. You should receive a email not to soon after this.

Error Logs

1. Task stays on Getting session for more than 30sec - This is most of the time a proxy issue try restarting your tasks. Note - This task might just be in queue make sure to check the logs and if they say Task in queue do not restart the task.

2. Access denied - Access denied can be explained as the proxy that the task is using is banned, or cookies used are not good. (These are soft bans which usually last for 30 min) Let the task run.

3. Datadome - Footsites new bot protection named "Datadome" has flagged your proxies and causing the to not pass the bot protection. (Change your proxies).

4. HTTPError: Response code 503 (Service Unavailable) - This can either be a proxy issue or the site is crashing or cant handle your requests. (If this continues to happen try changing your proxies).

5. Error code 429 - This is a proxy issue. It can be explained as the proxy is being rate limited.

6. Error sending billing - Error sending billing can be explained by - your proxy being banned after adding the item to cart - Note - Let the task run.

7. Couldn't checkout item - This can be related to many issues but just let the task run.

8. Tunneling and Time out - are proxy errors make sure to test your proxies before the drop with some test tasks (Run on any item) or proxy testers.

9. DataDome Ban - DataDome as you know security on footsites that is trying to stop you from doing a action, which could be getting session, Adding to cart, Sending your billing on Checkout, Or Even finishing the process of Checking out. Leave your Task running when this does happen