Platform cron jobs

Review scheduled jobs, run history, failures, and safe rerun procedures.

5 min readUpdated July 2026

Internal operator use

This article is for Flowforce platform operators, not normal tenant admins. Keep it in the operator academy unless Flowforce decides to publish internal admin training.

Video walkthrough placeholder showing cron job list, run history, failed state, and rerun control.
Video: Platform cron jobs
Video walkthrough placeholder showing cron job list, run history, failed state, and rerun control.
Internal platform screen showing cron job list, run history, failed state, and rerun control.
Internal platform screen showing cron job list, run history, failed state, and rerun control.

What to review

  • Open cron dashboard
  • Check last run and next run
  • Inspect failed jobs
  • Rerun only idempotent jobs when approved

Operating guardrails

  • Confirm the tenant or user before making changes.
  • Prefer read-only investigation before write actions.
  • Record the reason for support-impacting changes.
  • Escalate destructive or cross-tenant actions before proceeding.

Ready to try this in FlowForce?

Start free — set up your workspace and follow along with this guide.