docs: update cron trigger runs description

docs/jobs/state.md

@@ -148,19 +148,31 @@ The input state looks like this:
 
 ### Cron triggered runs
 
-On the platform, when a Run is triggered by a cron job, the input state will the
-final output state of the **last succesful run** for this workflow. This allows
-each subsequent run to _know_ about previous runs—i.e., you can pass information
-from one run to another even if they happen days apart.
+#### What are cron jobs?
+
+A **cron job** is a time-based scheduler that automatically runs your workflow at specified intervals. Think of it like setting an alarm clock for your workflow. It will run automatically at the times you configure, whether that's every hour, daily at 9 AM, or on the first day of each month.
+
+
+#### How cron input state works
+
+When a run is triggered by a cron job, the input state will be the final output state of the **last successful run** of the first step in the workflow. This allows each subsequent run to _know_ about previous runs. In other words, you can pass information from one run to another even if they happen days apart.
 
 ```js
 {
-  ...finalStateOfLastSuccessfulRun,
+  ...finalStateOfLastSuccessfulRunOfStep1,
 }
 ```
 
-If this is the first time the workflow has run, the initial state will simply by
-an empty Javascript object: `{}`
+**Example scenario**: You have a **daily sync at 9 AM** with a workflow that has 3 steps: (1) fetch patient records, (2) transform data, (3) send to database. On Monday, the **first step** processes records up to ID 1000 and outputs `{ lastProcessedId: 1000 }`. Even though steps 2 and 3 modify the state further, only the **first step's output** gets saved for the next cron run. On Tuesday at 9 AM, the cron job starts again with `{ lastProcessedId: 1000 }` from Monday's first step, so it knows to fetch records starting from ID 1001.
+
+If this is the first time the workflow has run, the initial state will simply be an empty JavaScript object: `{}`
+
+#### Overriding cron input
+
+You can always manually run a cron-triggered workflow with:
+- **Empty input**: `{}` - starts fresh without previous state.
+- **Custom input**: Your own data to test specific scenarios.
+- **Default input**: Uses the same input as the scheduled runs.
 
 ## Input & output state for steps