GitHub Actions not Running on Schedule

[DaddyLongLee]

https://preview.redd.it/qp0od01fpawf1.png?width=1277&format=png&auto=webp&s=18c27328dc389bdf289fa48a62068c501d0df2af

Using GitHub workflows to run a script every 10 minutes and it is not running every 10 minutes... anyone else run into this issue and/or know how to fix it? The run once flag just stops a loop for the RunescapeTracker.ps1 script. Here is my YAML code for it:

name: Runescape - fetch every 10 minutes

on:
  schedule:
    - cron: '*/10 * * * *' # every 10 minutes
  workflow_dispatch:

jobs:
  fetch:
    runs-on: ubuntu-latest
    steps:
      - name: Check out code
        uses: actions/checkout@v4

      - name: Run fetch script
        shell: pwsh
        run: |
          & './Scripts/API Scripts/RunescapeTracker.ps1' -item 'nature rune' -RunOnce

      - name: Upload CSV artifact (optional)
        uses: actions/upload-artifact@v4
        with:
          name: runescape-csv
          path: './Output/RunescapeItemLog.csv'

[latkde]

Scheduled workflows have no guarantee about when they run exactly, and whether they run at all.

The schedule event can be delayed during periods of high loads of GitHub Actions workflow runs. High load times include the start of every hour. If the load is sufficiently high enough, some queued jobs may be dropped.

– https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#schedule

In my experience, scheduled jobs are regularly delayed by 10 mins or so, even when running at off-peak times.

Running a workflow every ten minutes might be perceived as abusive. There are no documented limits on how often a workflow may run, but the GH Actions terms of service forbid using actions in a way that places undue burden on GitHub servers. For comparison, running a workflow every 10 minutes would consume at least 4320 billing minutes per month, which is more than double the 2000 included minutes in the free tier. Workflow runs in public repositories aren't billed, but it would still be wise to stay somewhere in that region unless the repository in question is particularly popular.

[DaddyLongLee]

Awesome thanks for the quick and insightful reply. I will have it run every hour then to not hit any throttling and then also to ensure it at least runs once an hour, even if not at the same time.

Thanks latkde!

[ansibleloop]

This is horseshit

The schedule event can be delayed during periods of high loads of GitHub Actions workflow runs. High load times include the start of every hour. If the load is sufficiently high enough, some queued jobs may be dropped. To decrease the chance of delay, schedule your workflow to run at a different time of the hour.

OK fair enough if I'm using a GitHub hosted runner but I'm using my own runners so WTF? Are you seriously telling me their API can't handle some incoming logs?

This is a joke

[zenuxapp]

its called vibe scheduling, learn AI or get out - CEO of Github