Manual Trigger Button for Payload Jobs in Admin UI

[ilhamsj]

Problem

Currently, Payload Jobs can only be triggered via:

• API
• Local API
• Code (hooks, cron, queues)

There is no way to manually trigger a job from the Admin UI.

This makes it difficult for:

• Admins / content editors
• Debugging & retrying failed jobs
• One-off jobs (imports, re-indexing, migrations)
• Non-technical users who don’t have API access

---

Proposed Solution

Add a “Run / Trigger Job” button in the Payload Admin UI:

• Available in the Jobs list view
• Or on the Job detail page
• Optional permission-based visibility (e.g. admin / developer roles)
• Optional confirmation modal
• Optional input override (advanced)

Example UX:

▶ Run Job

---

Use Cases

• Manually re-run failed jobs
• Trigger CSV imports without redeploying code
• Run maintenance jobs (reindex search, rebuild cache)
• QA / staging testing
• Operations & support teams

---

Suggested API (optional)

Internally, this could call the existing API:

payload.jobs.run({ job: jobID })

So this would be mainly an Admin UI enhancement, not a core job system change.

---

Why This Matters

• Improves developer experience
• Makes Jobs usable by non-engineers
• Reduces the need for custom endpoints / admin overrides
• Aligns with how other platforms handle background jobs (e.g. Rails ActiveJob, Laravel Horizon)

---

Workaround Today

Currently requires:

• Custom endpoint
• Custom admin component
• Manual wiring

A first-class UI solution would simplify this significantly.

[shomriddho]

I Agree ☝️