Restarts Now Available When Using HyperBatch

“Restart HIT” Using HyperBatch

The CloudResearch “Restart” feature (which Restarts HITs that have become sluggish; see our blog post on Restarts to see all the benefits of this feature) can now be used in conjunction with HyperBatch. This was a highly requested feature from our users and we are happy to announce that it is now LIVE. The only difference between using the restart feature with HyperBatch and using the restart feature without HyperBatch is that you will only be able to restart the HIT once per day with HyperBatch. This helps ensure that our system will not be over-burdened.

However, as always, when workers view HITs, they now find your HIT at the top of the MTurk HIT Dashboard. When restarted, HITs that have aged and have become hard to see by MTurk Workers will have the visibility of a brand new HIT – because CloudResearch has created a new HIT and associated it with the same specifications as your original HIT.

Additionally, when using Restart, Workers who have completed your original HIT are automatically excluded from taking the newly created HIT and are unable to accept the HIT because CloudResearch has created a Qualification Type that excludes them!

There is nothing that a Requester needs to set up to enable the Restart feature. It appears in the CloudResearch Dashboard as soon as your HIT goes Live.

For more on the benefits of using HyperBatch, check out our blog post.