One of the challenges reported to us during the beta testing phase has been problems with running tests too close together. To counter this we’ve now gone live with some enhancements to the test scheduling engine.
The first change is we’ve increased the frequency available for running tests with intervals now starting at every 6 minutes for 10 tests per hour per test. Additionally, in order to handle problems with APIs handling multiple incoming requests, we’ve introduced an offset option. This allows you to specify a timing offset for when each test will trigger – this should get around any API timing conflicts you encounter.
As always you can contact us with any issues or feature requests.
If you’re not already a user why not sign up today and try us out today.
