:verbose: true
:concurrency: 8
:logfile: ./log/sidekiq.json.log
:queues:
  - scheduled_publishing
  - default
  - publishing_api
  - asset_manager
  - email_alert_api_signup
  - bulk_republishing
  - link_checks
  - asset_migration
:schedule:
  check_all_organisations_links_worker:
    cron: '0 3 * * *' # Runs at 3 a.m every day
    class: CheckAllOrganisationsLinksWorker

:verbose: true
:concurrency: 8
:logfile: ./log/sidekiq.json.log
:queues:
  - scheduled_publishing
  - default
  - publishing_api
  - asset_manager
  - email_alert_api_signup
  - bulk_republishing
  - link_checks
  - asset_migration
:schedule:
  check_all_organisations_links_worker:
    cron: '0 4 * * *' # Runs at 4 a.m every day
    class: CheckAllOrganisationsLinksWorker

Change start time of CheckAllOrganisationsLinksWorker
Change start time of CheckAllOrganisationsLinksWorker

This commit changes the start time of `CheckAllOrganisationsLinksWorker` from `03:00` to `04:00`.

We have been seeing a number of errors for `CheckOrganisationLinksWorker` (called by `CheckAllOrganisationsLinksWorker` for every organisation) which indicate that the `editions` database table doesn't exist.

The Whitehall database is synced from production to staging at 03:00 everyday (https://github.com/alphagov/govuk-puppet/blob/f1716ae4be57832c3f1e57f93e95646908f799c4/hieradata_aws/class/staging/db_admin.yaml#L136). From the logs this takes approximately 20 minutes, after which these particular errors desist until the next day at 03:00.

By moving the time that the worker starts forwards by one hour, we allow the database sync to complete.
