anchor.diff:      <tr><th><code>@daily</code> or <code>@midnight</code></th><td>Every day at midnight UTC</td><td><code>0 0 * * *</code></td></tr>
       <tr><th><code>@weekly</code></th><td>Every week at midnight Sunday UTC</td><td><code>0 0 * * 0</code></td></tr>
       <tr><th><code>@monthly</code></th><td>Every month, at midnight UTC on the first day</td><td><code>0 0 1 * *</code></td></tr>
  +    <tr><th><code>@yearly</code></th><td>Every year, at midnight UTC on the first day</td><td><code>0 0 1 1 *</code></td></tr>
     </tbody>
   </table>
   
  
positive.code:  │ │ │ │ │          ┌─── time zone name or offset (optional)
   │ │ │ │ │          │
   * * * * * Australia/Melbourne
  ```
  
  Buildkite uses the [Fugit](https://github.com/floraison/fugit) ruby gem for parsing cron strings, so features they support such as modulo are also supported by Buildkite schedules. See the [Fugit::Cron documentation](https://github.com/floraison/fugit#fugitcron) for more information and examples.   
  
  A time zone can optionally be specified as the last segment, either as an [IANA Time Zone name](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) like `Australia/Melbourne` or `Europe/Berlin`, or as an offset from UTC like `+09:00` or `-05:00`. If no time zone is given, the schedule will run in UTC.
  
  Examples:
  
  <table>
    <tr><th><code>*/10 * * * *</code></th><td>Every 10 minutes</td></tr>
  
negative.code: 
  ### Predefined intervals
  
  Buildkite supports 6 predefined intervals:
  
  <table>
    <thead>
  