Nebula Omega utilizes two different modes for task checkouts on Footsites: RESTOCK and RELEASE. The idea to successfully use Nebula Omega on Footsites is to have numerous amounts of tasks initialize checkout processes increasing the likelihood of success with the more tasks ran. Generating cookies are NOT needed.


• Fast checkout flow optimized for restocks


• For queue handling on initial release


• Utilize the One Checkout For Profile feature to prevent duplicate checkouts on the same profile / reduce cancellations.

• Enable proxy rotation (in advanced task creation settings) for captcha bypass. Do not use this on initial release or when queue is live

Did this answer your question?