The way PrismAIO 2.0 monitors for a product is very different than many bots and 1.0. For starters, what does it mean by "monitoring"? Monitoring is the process of waiting for a product to become in-stock or for the product to be "live".

In a task group, you will notice a proxy list option on the left-hand side in the task group as seen below.

In that proxy list box, you will choose a proxy list for MONITORING ONLY. This means that the group itself is what will do the monitoring, TASKS DO NOT DO INDIVIDUAL MONITORING. For instance, if you see your bot on "Waiting for Product" that means that each individual task is waiting for the task group to find the product using the task group proxies. The only exception to this comes if your Shopify task becomes OOS while you are checking out, or if you are using variants. If this is the case, the bot will use the TASK proxies to monitor for that SPECIFIC size to come back in stock.

In even simpler terms, this means that the task group is in charge of finding the product and the tasks are in charge of checking them out.


What are "threads" A.K.A "monitor workers"?

  • Threads in simpler terms are like another monitoring task. The max threads the bot will use is 10. This is swiftly calculated by the bot to insure that your monitor proxies will not become banned. The bot takes into account a variety of factors, including how many proxies you have in the task group list, what your current task group delay is, and lastly what our "unbannable delay" is.

How much data do monitor "threads" use?

  • Monitor threads use roughly the same amount of data as a single task. With this though, the task group monitor is only looking for the product and in-stock sizes, and it does add-to-cart or checkout attempts which tries to save on data.

If my tasks have residential (resi) proxies as the TASK proxies and datacenter (DC) proxies as the MONITOR proxies, will they use data if the tasks are on "Waiting for Product"?

  • No, the tasks will not use the residential proxies to monitor for the product. If the tasks are on "Waiting for Product" or "Waiting for Restock", they will use the DC proxies that are the monitor proxies to wait for the product to be live. The only case where the task will use the residential is if the site you are running is Shopify and the task proceeds to checkout but the product goes OOS. In that case, the task will CONTINUE to use the task proxies, in this case the residential ones.

How many monitor proxies do I need?

  • There is no set amount, but the more the better. If you run very low monitor delays, it is best to have many (25+) proxies.

Can I use no proxies (localhost) as the task group proxies?

  • You can, but it is not recommended to do it for more than 1 task group per site. So if you are running 5 task groups for Finish Line, don't run more that 1 task group without task group proxies.

    Pro-tip: If you are running on a Shopify site with proxy protection and your datacenter proxies are throttled, run one task group on your localhost and your tasks with residential proxies. In this case, the bot should pickup the product faster rather than using residential proxies to monitor as they often are slower speeds.

Do the group proxies have to be the same as the task proxies?

  • No they do not. You can use two different groups for both - it does not matter if they are the same or not.

Did this answer your question?