cron:
- description: Syncs employee data from s3
  url: /tasks/populate_employees
  schedule: every day 03:00
  timezone: America/Los_Angeles
  target: api

- description: clean user subscriptions
  url: /tasks/clean_user_subscriptions
  schedule: every day 4:00
  timezone: America/Los_Angeles
  target: api

- description: weekly meeting spec generation
  url: /tasks/generate_meeting_specs_for_week
  schedule: every monday 6:00
  timezone: America/Los_Angeles
  target: api

- description: weekly opt-in email
  url: /tasks/email_users_for_weekly_opt_in
  schedule: every monday 9:00
  timezone: America/Los_Angeles
  target: api

- description: weekly match
  url: /tasks/match_employees
  schedule: every tuesday 11:00
  timezone: America/Los_Angeles
  target: api

cron:
- description: Syncs employee data from s3
  url: /tasks/populate_employees
  schedule: every day 03:00
  timezone: America/Los_Angeles
  target: api

- description: clean user subscriptions
  url: /tasks/clean_user_subscriptions
  schedule: every day 4:00
  timezone: America/Los_Angeles
  target: api

- description: weekly meeting spec generation
  url: /tasks/generate_meeting_specs_for_week
  schedule: every monday 6:00
  timezone: America/Los_Angeles
  target: api
  retry_parameters:
    min_backoff_seconds: 30

- description: weekly opt-in email
  url: /tasks/email_users_for_weekly_opt_in
  schedule: every monday 9:00
  timezone: America/Los_Angeles
  target: api

- description: weekly match
  url: /tasks/match_employees
  schedule: every tuesday 11:00
  timezone: America/Los_Angeles
  target: api

Add retries for the weekly meeting spec generation batch
Add retries for the weekly meeting spec generation batch

Made the min_backoff_seconds fairly big to help ensure what caused the
issue was resolved and we have 3 hours to successfully run this job.
Also the default of 5 retries seemed fine, so it didn't seem worth
messing with.
