Github actions job timeout

Question

I have a GitHub workflow with long-running job (10 hours). Even though I have configured the timeout-minutes in the job it gets canceled within 6 hours. Is there a limitation?

name: Spawn cluster

on:
  workflow_dispatch:
  schedule:
    - cron:  '0 */12 * * *'
jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 600
    steps:
    - name: CHECKOUT
      uses: actions/checkout@v2
    - name: AZURE LOGIN
      uses: azure/login@v1
      with:
        creds: ${{secrets.AZURE_CREDENTIALS}}

Answer 1

Yeah, there are some limits

• Job execution time - Each job in a workflow can run for up to 6 hours of execution time. If a job reaches this limit, the job is terminated and fails to complete.

• Workflow run time - Each workflow run is limited to 72 hours. If a workflow run reaches this limit, the workflow run is cancelled.

• API requests - You can execute up to 1000 API requests in an hour across all actions within a repository. If exceeded, additional API calls will fail, which might cause jobs to fail.

• Concurrent jobs - The number of concurrent jobs you can run in your account depends on your GitHub plan, as indicated in the following table. If exceeded, any additional jobs are queued.

So probably if you need to run a 10-hour job you need to have a self-hosted agent. Or try to split this into smaller chunks.