---
title: "Comment by Hayrullah Kar on \"Why your GitHub Actions cron runs late, and how to start it on time\" | Hashnode"
description: "The list of what a 401, 404 and 422 mean will save someone a confused afternoon. One thing to plan for: that token belongs to a person, so the schedule stops if"
url: "https://hashnode.com/posts/why-your-github-actions-cron-runs-late-and-how-to-start-it-on-time/6afbbce1a09f9d08ef7dbb49/comment/6afbf9529dae916a762bb2ad"
---

[Discussion](https://hashnode.com/posts/why-your-github-actions-cron-runs-late-and-how-to-start-it-on-time/6afbbce1a09f9d08ef7dbb49)

Comment [Why your GitHub Actions cron runs late, and how to start it on time](https://hashnode.com/posts/why-your-github-actions-cron-runs-late-and-how-to-start-it-on-time/6afbbce1a09f9d08ef7dbb49)

[Hayrullah Kar](https://hashnode.com/@magesheet)

[2d ago](https://hashnode.com/posts/why-your-github-actions-cron-runs-late-and-how-to-start-it-on-time/6afbbce1a09f9d08ef7dbb49/comment/6afbf9529dae916a762bb2ad)

The list of what a 401, 404 and 422 mean will save someone a confused afternoon. One thing to plan for: that token belongs to a person, so the schedule stops if they leave the org or their access changes. In organisations that require approval for fine-grained tokens, it may not work until an owner approves it. A GitHub App installation token avoids both, if your scheduler can mint one..
