Use the scheduler to schedule when a test should run.
The scheduled tests should be active, so they should retrieve the resources on their own using a GET/POST/PUT/DELETE I/O operations.

From the test interstitial page

Select Schedule and “Create new run”.

Name: the name of the run. Makes it easy to recognize it from a list
Paused: if checked, the run won’t trigger executions
Downloader: choose from which datacenter the resources should be retrieved from
Try a second execution…: if a test execution fails, another execution will be run after 2m 30s
Time configuration – minutes: in which minutes of the hour the test is going to run. Minimum interval is 5 minutes. Mind that freemium contracts could have reduced options
Time configuration – hours: in which hours of the day the test is going to run
Time configuration – days: in which days of the month the test is going to run
Time configuration – months: in which months of the year the test is going to run

Note: the scheduler works by intersecting the provided settings.
Example: set minutes: 5,15 and days: 1,5. The test will run every hour at minute 5 and 15, only if the day is either 1 or 5.

Overrides:┬áthis section allows you to override any variable that is defined in the global section or in data set. For example, if you wrote a test against your production environment and want to keep an eye on how the staging environment reacts to the same test, you can override the ‘domain’ variable with the staging domain for a specific scheduled item that will therefore run the test altering the target host.