doctl apps list-job-invocations returns empty results when invocations exist

[stuboo]

Bug Report

doctl version

doctl version 1.152.0-release

Description

doctl apps list-job-invocations <app-id> <job-name> returns an empty table with no results, even when the job has many invocations recorded by the platform.

Steps to Reproduce

1. Create an App Platform app with a scheduled job (kind: SCHEDULED)
2. Wait for the job to be invoked (either by the scheduler or manually)
3. Run doctl apps list-job-invocations <app-id> <job-name>

Expected Behavior

The command should list all job invocations with their ID, phase, timestamps, etc.

Actual Behavior

The command returns an empty table:

$ doctl apps list-job-invocations <app-id> cron-test
ID    Job Name    Created At    Started At    Completed At    Phase

However, the underlying API returns data correctly:

$ curl -s -H "Authorization: Bearer $TOKEN" \
  "https://api.digitalocean.com/v2/apps/<app-id>/jobs/<job-name>/invocations" | python3 -m json.tool

Returns 13 invocations, all with phase: SUCCEEDED.

Impact

This bug masked the real issue with our scheduled jobs — we spent hours thinking the cron scheduler was never firing, when in fact jobs were being invoked and failing. The empty CLI output made it appear that no invocations had ever occurred.

Workaround

Use the API directly via curl.

Environment

• OS: macOS (Darwin 24.2.0)
• doctl version: 1.152.0-release
• Shell: zsh

[anup-deka]

It looks like API is returning empty list of job invocations

[anup-deka]

Fixed in #1824