Running a Release

Overview

This guide will show you the correct way to run a release and the steps you need to take to be able to monitor and check the progress of your tasks.

Please note that there are many ways you can configure the software and some may yield better results than others – it’s up to you to familiarise yourself with the documentation and experiment.

Don’t forget we’re here to help. Contact Us if you need any additional support in using the software.

Step 1: Preparing for the Release

Follow the basic set-up guide in order to prepare for the release. (See Images 1, 2, 3)

Click here to follow the basic set-up guide.

Step 2: Starting the Release

You can either start your release manually or schedule your release to start. We recommend starting your release around 15 – 30 seconds prior to the release. (See Images 1, 2)

Click here to learn more about scheduling your release.

Step 3: Monitoring the Release

Once you have started your release, you will be able to see your Global Log and Task Log. These logs will show you the progress of your tasks during the release, as well as the times associated with each task. (See Images 1, 2, 3)

Click here to learn more about the Global Log.

Click Here to learn more about the Task Log.

Step 4: Aborting your Tasks

You can abort your tasks at any time by clicking End All Tasks. If you need to change any information from your task profile during the release, you will need to end your tasks first in order to alter them.  (See Images 1,2)

Step 5: Checking Success

If your task(s) successfully check out, you can view the confirmed items in the Success Monitor. (See Image 1)

Click here to learn more about the Success Monitor.

Step 6: Common Errors

When running the release, you may receive some errors which can occur for various reasons.

Please see below for a list of the most common errors:

  1. NoMatchingStyle – If you receive this error, you have either put in the wrong keywords, incorrectly spelt them or the item does not exist/not releasing.  (See Image 1)
  2. NoSizeMatch – If you receive this error, the size you have requested is not correct for the product. (See Image 2)
  3. SoldOut – If you receive this error, then the item is no longer available; It can also mean the item is no longer available in the specific size or colour you requested. (See Image 3)
  4. CheckoutError – This error indicates that Supreme have found a problem with your checkout profile, you should receive an short explanation of the error in the following line, such as card details being incorrect. (See Image 4)
  5. Queued – Supreme have a queuing system, and if Queued appears it is just a symptom of Supreme’s checkout system. (See Image 5)
  6. CannotProcessPayment – There are several reasons for this error, which may include: invalid card details, bad proxies, incorrect captcha timestamp, banned address or card details. (See Image 6)
  7. HttpError – This error occurs if the bot is unable to access Supreme’s website because of an IP ban, lost internet connection or banned proxies. It may also appear during a crash on the website. (See Image 7)
  8. ProxyAuthenticationRequired – If you receive this error then you do not have the correct username or password for the proxy. We recommend contacting your proxy provider regarding this. (See Image 8)
  9. DuplicateOrder – This means that the product has already been purchased with your billing information; once this response occurs, the tasks associated with it will automatically stop running. (Image 9)
  10.  CartRedirect  – This response is cart jacking, whereby one or more items are trying to checkout but no longer exist due to being sold out. (Image 10)

Summary

There you have it! Feel free to browse the rest of the documentation as there are numerous ways to configure the software and some may yield better results than others.

If you are unable to find the answer you are looking for within this documentation, feel free to get in touch with us today!