GET /api/v1/issues.
Why something stopped
An issue opens when the condition starts and resolves when it ends - a worker or a database is not started again by a retry on your part: a worker comes back with the next deploy, and an application, service, or add-on starts again once its cause is fixed (more memory, room on its resource, or Usage Billing started).
Filtering
In the dashboard, open an application, service, or resource’s own page to see only its issues. Over the API, filterGET /api/v1/issues with one of:
app_id- an application and everything under it: its own issues, its workers’, and its cron jobs’service_id- a standalone serviceresource_id- a resource, and everything running on it that you can see
400.
Leaving all three out does not return every issue you can see. It is narrowed to whichever of apps:view, services:view, and resources:view you hold, one kind at a time - a role with only apps:view sees application, worker, and cron job issues but no service or resource ones, with no error to say so.
What an issue carries
subject- what stopped: itstype(app,worker,addon,service, orcronjob),uuid,name, andlabelopen- true until it is resolvedopened_at/resolved_atdetails- specific to the kind: requested and allowed replicas forout_of_capacity; restart count (and, for an add-on, the exit code and the last lines of its log) for a crash; a failed run’s job name, reason, exit code, and message forcronjob_failed
Next steps
Webhooks
Get notified the moment something stops, instead of polling Issues.
Worker processes
Where a worker’s own issues come from.

