Merge pull request #82 from buildkite/docs-public-pr-2961

Job expiry process delays

pages/pipelines/build_timeouts.md

@@ -38,3 +38,6 @@ By default, jobs are canceled when not picked up for 30 days. This will cause th
 You can override the default by setting a shorter value in your organization's [**Pipeline Settings**](https://buildkite.com/organizations/~/pipeline-settings) page.
 
 Scheduled job limits should not be confused with [scheduled builds](/docs/pipelines/scheduled-builds). A scheduled build's jobs will still go through the [build states](/docs/pipelines/defining-steps#build-states), and the timeout will apply once its individual jobs are in the scheduled state waiting for agents.
+
+> 📘 Delays in job expiration
+> A job's expiration process is run hourly at 5 minutes past. When the expiration process runs and the job's scheduled expiration was not over at that hour, it will only be expired until the next hour when the process is executed again.