Incidents

High severity incidents

Incident groups currently marked high severity. Captured errors come from debug_logs and system_logs grouped at request time. Agent work tickets are separate Convex records linked to these error groups.

All incidents

23

Critical

0

High severity

20

Affected routes

16

High severity incidents

20 grouped incidents in the current view

Page 1 of 2

IncidentRouteSurfaceSeverityCountTicketSeen
error.gcp.generic.cloud_run_job

Execution user-welcome-email-signup-production-8kcx2 has failed to complete, 0/1 tasks were a success.

cloud_logginggcphigh113No ticket11m
error.frontend.handled

Failed to fetch

/generatefrontendhigh45No ticket7h
error.frontend.handled

Failed to fetch

/frontendhigh7No ticket7h
cloud_scheduler_job/monitor-news-social-scheduler-productiongcphigh1No ticket16h
/backendhigh9No ticket1d
error.frontend.handled

Failed to fetch

/onboarding/offer/pixverse-v5-5frontendhigh2No ticket1d
error.frontend.handled

Failed to fetch

/onboarding/modelsfrontendhigh2No ticket1d
error.frontend.handled

Failed to fetch

/onboarding/offer/veo_3frontendhigh1No ticket1d
error.frontend.handled

Failed to fetch

/supportfrontendhigh1No ticket1d
error.frontend.handled

Failed to fetch

/generate/3073d2db-6c4d-48ba-a6a0-35ffa1ab4814/70198fcf-0d6d-4efd-b90b-f1b4752932e9frontendhigh2No ticket1d
Showing 1-10 of 20 incidents
PreviousNext

Incident details

error.gcp_cloud_run.monitor_news_publish_worker.request_failed

GCP error log captured

Severity
high
Surface
backend
Route
/
Function
monitor-news-publish-worker
Location
cloud_logging
Source table
debug_logs
Occurrences
9
Last seen
Jul 20, 05:27 PM

Occurrence history

GCP error log captured

/ · backend · debug_logs

monitor-news-publish-worker

cloud_logging

high

Jul 20, 05:27 PM

GCP error log captured

/ · backend · debug_logs

monitor-news-publish-worker

cloud_logging

high

Jul 20, 05:27 PM

GCP error log captured

/ · backend · debug_logs

monitor-news-publish-worker

cloud_logging

high

Jul 20, 05:27 PM

The request was aborted because there was no available instance. Additional troubleshooting documentation can be found at: https://cloud.google.com/run/docs/troubleshooting#abort-request

/ · backend · debug_logs

monitor-news-publish-worker

cloud_logging

high

Jul 20, 05:27 PM

The request was aborted because there was no available instance. Additional troubleshooting documentation can be found at: https://cloud.google.com/run/docs/troubleshooting#abort-request

/ · backend · debug_logs

monitor-news-publish-worker

cloud_logging

high

Jul 20, 05:27 PM

The request was aborted because there was no available instance. Additional troubleshooting documentation can be found at: https://cloud.google.com/run/docs/troubleshooting#abort-request

/ · backend · debug_logs

monitor-news-publish-worker

cloud_logging

high

Jul 20, 05:27 PM

The request was aborted because there was no available instance. Additional troubleshooting documentation can be found at: https://cloud.google.com/run/docs/troubleshooting#abort-request

/ · backend · debug_logs

monitor-news-publish-worker

cloud_logging

high

Jul 20, 05:27 PM

The request was aborted because there was no available instance. Additional troubleshooting documentation can be found at: https://cloud.google.com/run/docs/troubleshooting#abort-request

/ · backend · debug_logs

monitor-news-publish-worker

cloud_logging

high

Jul 20, 05:27 PM

The request was aborted because there was no available instance. Additional troubleshooting documentation can be found at: https://cloud.google.com/run/docs/troubleshooting#abort-request

/ · backend · debug_logs

monitor-news-publish-worker

cloud_logging

high

Jul 20, 05:27 PM