Skip to main content

Run & schedule

A workflow is only useful when it runs. You can run one on demand, run a single step, or set it to run automatically.

Run on demand​

Press Run Workflow in the toolbar. JobKred validates the graph, starts the run, and the button changes to Cancel Run while it's working. Progress appears node by node as each step completes.

Runs don't depend on your browser

Workflows run on our servers, not in your tab. You can close the app and come back — a long run keeps going. Cancelling stops it cleanly between steps rather than mid-way through one.

Run a single node​

While building or debugging, use Run Node in the Inspector to execute just one step. See Build a workflow.

Schedule automatic runs​

Open the Schedule tab to have a workflow run on a cadence — no one needs to press a button.

Set a frequency and time:

  • Daily — every day at a set hour and minute.
  • Weekly — on chosen day(s) of the week.
  • Monthly — on a chosen day of the month.
  • Yearly — on a chosen date.

The schedule table shows each schedule's status, its frequency, the schedule itself (the day and time it fires), the next run, and the last run with its result. For each one you can Pause / Activate, Edit, or Delete.

Status reads Active or Paused most of the time. Around a scheduled moment you'll briefly see Running soon — the run has come due and is being picked up.

The results come to you

When a scheduled run finishes successfully, JobKred emails its artifacts to the workflow's owner. So a monthly Workforce Diagnostic lands in your inbox as well as in the Artifacts tab — no need to remember to go and look.

Common pattern

Schedule a quarterly Skill Gap Analysis or a monthly Workforce Diagnostic so the latest reports are always waiting for you.

Review run history​

The Run Log tab records every run — manual and scheduled — from two angles:

  • Workflow Executions — one row per run: when it started, how it ended, how long it took.
  • Node Executions — one row per step, so you can find the single node that failed or produced something unexpected.

For a visual read of a single run, open the Timeline tab. It lays the run out as a bar chart of node executions, which makes it obvious which steps ran in parallel and which one was the bottleneck.

Next step​

Work with the reports your runs produce → Artifacts & exports.