molecule-ai/molecule-core
52
0
Fork 2
Code Issues 179 Pull Requests 57 Actions 10 Packages Projects Releases Wiki Activity

ScheduleHandler routes never mounted in cmd/server/main.go — schedule CRUD API returns 404 in prod #1692

New Issue
Closed
opened 2026-05-22 23:34:12 +00:00 by hongming · 1 comment
hongming commented 2026-05-22 23:34:12 +00:00
Owner
Copy Link
Copy Source

Bug

workspace-server/internal/handlers/schedules.go declares a full ScheduleHandler with List / Create / Update / Delete / RunNow / History methods. But the handler is never instantiated in workspace-server/cmd/server/main.go — NewScheduleHandler() has zero callers.

Consequence:

  • GET / POST /workspaces/:id/schedules returns 404 in prod
  • The Canvas Schedule tab + any external scheduler-create flow is broken
  • The scheduler background loop (cronSched.Start) DOES run + DOES fire scheduled prompts (verified — it polls workspace_schedules table directly), but there is no public way to CREATE a schedule beyond direct SQL

Verified 2026-05-22 23:14Z:

  • POST agents-team.moleculesai.app/workspaces/deedcb61-.../schedules → 404
  • POST api.moleculesai.app/cp/admin/workspaces/.../schedules → 404
  • GET api.moleculesai.app/cp/admin/schedules → 404
  • grep -n NewScheduleHandler workspace-server/cmd/server/main.go → 0 matches

Fix

5-line patch in workspace-server/cmd/server/main.go, alongside existing handler mounting:

sh := handlers.NewScheduleHandler()
engine.GET("/workspaces/:id/schedules", sh.List)
engine.POST("/workspaces/:id/schedules", sh.Create)
engine.PATCH("/workspaces/:id/schedules/:sid", sh.Update)
engine.DELETE("/workspaces/:id/schedules/:sid", sh.Delete)
engine.POST("/workspaces/:id/schedules/:sid/run", sh.RunNow)
engine.GET("/workspaces/:id/schedules/:sid/history", sh.History)

Plus the existing requireWorkspaceToken / CanCommunicate auth middleware applied to the group, matching the patterns used for other workspace-scoped CRUD handlers.

Why it matters

  • Blocks the PM autonomous-cron SOP (Kimi/MiniMax 24/7 dispatch — see feedback_kimi_minimax_default_dispatch_2026_05_22)
  • Blocks any Canvas-side schedule management UX
  • The scheduler infrastructure (cron expr parse, fire timing, A2A dispatch, history, phantom sweep, native-scheduler-skip) is ALL there and working — only the HTTP face is missing

Acceptance

  • 6 routes registered + auth-gated
  • Smoke test: curl -X POST -H Authorization: Bearer <ws-token> /workspaces/:id/schedules -d ... → 201
  • E2E: create a schedule via API, verify next_run_at advances + cron fires per workspace_schedules.run_count

Owner

TBD. Estimated ~2h including tests.

## Bug `workspace-server/internal/handlers/schedules.go` declares a full `ScheduleHandler` with `List` / `Create` / `Update` / `Delete` / `RunNow` / `History` methods. But the handler is **never instantiated** in `workspace-server/cmd/server/main.go` — `NewScheduleHandler()` has zero callers. Consequence: - `GET / POST /workspaces/:id/schedules` returns **404 in prod** - The Canvas Schedule tab + any external scheduler-create flow is broken - The scheduler background loop (`cronSched.Start`) DOES run + DOES fire scheduled prompts (verified — it polls `workspace_schedules` table directly), but there is no public way to CREATE a schedule beyond direct SQL Verified 2026-05-22 23:14Z: - `POST agents-team.moleculesai.app/workspaces/deedcb61-.../schedules` → 404 - `POST api.moleculesai.app/cp/admin/workspaces/.../schedules` → 404 - `GET api.moleculesai.app/cp/admin/schedules` → 404 - `grep -n NewScheduleHandler workspace-server/cmd/server/main.go` → 0 matches ## Fix 5-line patch in `workspace-server/cmd/server/main.go`, alongside existing handler mounting: ```go sh := handlers.NewScheduleHandler() engine.GET("/workspaces/:id/schedules", sh.List) engine.POST("/workspaces/:id/schedules", sh.Create) engine.PATCH("/workspaces/:id/schedules/:sid", sh.Update) engine.DELETE("/workspaces/:id/schedules/:sid", sh.Delete) engine.POST("/workspaces/:id/schedules/:sid/run", sh.RunNow) engine.GET("/workspaces/:id/schedules/:sid/history", sh.History) ``` Plus the existing `requireWorkspaceToken` / `CanCommunicate` auth middleware applied to the group, matching the patterns used for other workspace-scoped CRUD handlers. ## Why it matters - Blocks the PM autonomous-cron SOP (Kimi/MiniMax 24/7 dispatch — see `feedback_kimi_minimax_default_dispatch_2026_05_22`) - Blocks any Canvas-side schedule management UX - The scheduler infrastructure (cron expr parse, fire timing, A2A dispatch, history, phantom sweep, native-scheduler-skip) is ALL there and working — only the HTTP face is missing ## Acceptance - 6 routes registered + auth-gated - Smoke test: `curl -X POST -H Authorization: Bearer <ws-token> /workspaces/:id/schedules -d ...` → 201 - E2E: create a schedule via API, verify `next_run_at` advances + cron fires per `workspace_schedules.run_count` ## Owner TBD. Estimated ~2h including tests.
hongming commented 2026-05-23 00:20:56 +00:00
Author
Owner
Copy Link
Copy Source

Closing — incorrect diagnosis. Schedule routes ARE mounted in workspace-server/internal/router/router.go (lines 374-385 of origin/main, the schedh := handlers.NewScheduleHandler() block under wsAuth). My grep on main.go missed this because the wiring lives in router.go, not main.go.

If PM is still 404-ing on schedule endpoints, the real gap is somewhere else — needs a fresh investigation:

  • Does the agent runtime SDK expose a set_schedule MCP tool that calls POST /workspaces/:id/schedules?
  • Is the Canvas Schedule tab using the correct WorkspaceAuth bearer + URL shape?
  • Is the Temporal cron worker actually fired up in this deployment?

Reopening once I have the actual broken layer identified.

Closing — incorrect diagnosis. Schedule routes ARE mounted in `workspace-server/internal/router/router.go` (lines 374-385 of origin/main, the `schedh := handlers.NewScheduleHandler()` block under `wsAuth`). My grep on main.go missed this because the wiring lives in router.go, not main.go. If PM is still 404-ing on schedule endpoints, the real gap is somewhere else — needs a fresh investigation: - Does the agent runtime SDK expose a `set_schedule` MCP tool that calls `POST /workspaces/:id/schedules`? - Is the Canvas Schedule tab using the correct WorkspaceAuth bearer + URL shape? - Is the Temporal cron worker actually fired up in this deployment? Reopening once I have the actual broken layer identified.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/ci
CI/CD pipeline issues
 do-not-auto-merge
Opt out of autonomous merge-queue merging
 kind/infrastructure
Infrastructure-related issues
 merge-queue
Ready for serialized Gitea merge queue
 merge-queue-hold
Temporarily hold PR in merge queue
 platform/go
Go platform test issues
 release-blocker
Blocks the staging→main promotion / a release
 release-test
security
test-label-sre
tier:high
High risk per dev-sop §SOP-6 — ceo only, 24h cooldown
 tier:low
Low risk per dev-sop §SOP-6 — engineers/managers/ceo can approve
 tier:medium
Medium risk per dev-sop §SOP-6 — managers/ceo can approve
 triage-test
test
 wip
Work in progress — do not auto-merge
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agent-dev-a agent-dev-b agent-pm agent-researcher agent-reviewer agent-reviewer-1 agent-reviewer-cr2 app-fe (Molecule AI · app-fe) app-lead (Molecule AI · app-lead) app-qa (Molecule AI · app-qa) claude-ceo-assistant claude-ci-reader claude-status-reaper core-be (Molecule AI · core-be) core-devops (Molecule AI · core-devops) core-fe (Molecule AI · core-fe) core-lead (Molecule AI · core-lead) core-offsec (Molecule AI · core-offsec) core-qa (Molecule AI · core-qa) core-security (Molecule AI · core-security) core-uiux (Molecule AI · core-uiux) cp-be (Molecule AI · cp-be) cp-lead (Molecule AI · cp-lead) cp-qa (Molecule AI · cp-qa) cp-security (Molecule AI · cp-security) cui (Zhanlin Cui) dev-lead (Molecule AI · dev-lead) devops-engineer documentation-specialist (Molecule AI · documentation-specialist) fullstack-engineer (Molecule AI · fullstack-engineer) godwin hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 infra-lead (Molecule AI · infra-lead) infra-runtime-be (Molecule AI · infra-runtime-be) infra-sre (Molecule AI · infra-sre) integration-tester (Molecule AI · integration-tester) mc-drift-bot molecule-code-reviewer plugin-dev (Molecule AI · plugin-dev) pm publish-runtime-bot pypi-publisher (Molecule AI PyPI Publisher (RFC#596)) release-manager (Molecule AI · release-manager) sdk-dev (Molecule AI · sdk-dev) sdk-lead (Molecule AI · sdk-lead) sop-drift-bot sop-tier-bot (SOP Tier-Check Bot) technical-writer (Molecule AI · technical-writer) triage-operator (Molecule AI · triage-operator)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#1692
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?