Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix UI: Cron/Schedules component fails to load due to API endpoint mismatch [1 pull requests]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

There is a mismatch between the frontend API calls and the backend routing for managing cron jobs.

  • Frontend: web/src/lib/api.ts requests GET /api/cron/jobs.
  • Backend: gateway/platforms/api_server.py defines the route as GET /api/jobs.

This results in the "Schedules" section of the web UI remaining empty or showing errors, even when jobs are correctly defined in jobs.json.

Root Cause

There is a mismatch between the frontend API calls and the backend routing for managing cron jobs.

  • Frontend: web/src/lib/api.ts requests GET /api/cron/jobs.
  • Backend: gateway/platforms/api_server.py defines the route as GET /api/jobs.

This results in the "Schedules" section of the web UI remaining empty or showing errors, even when jobs are correctly defined in jobs.json.

Fix Action

Fixed

RAW_BUFFERClick to expand / collapse

Description

There is a mismatch between the frontend API calls and the backend routing for managing cron jobs.

  • Frontend: web/src/lib/api.ts requests GET /api/cron/jobs.
  • Backend: gateway/platforms/api_server.py defines the route as GET /api/jobs.

This results in the "Schedules" section of the web UI remaining empty or showing errors, even when jobs are correctly defined in jobs.json.

Suggested Fix

Align the backend route to match the frontend's expectation, or update the frontend to use the existing /api/jobs endpoint. (Note: Adding support for the profile query parameter in this endpoint would also improve multi-profile isolation).

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix UI: Cron/Schedules component fails to load due to API endpoint mismatch [1 pull requests]