docs: update cron trigger runs description

[hunterachieng]

Short Description

Update cron trigger runs description to make it easy to understand

Closes #680

Details

AI Usage

Please disclose how you've used AI in this work (it's cool, we just want to
know!):

• Code generation (copilot but not intellisense)
• Learning or fact checking
• Strategy / design
• Optimisation / refactoring
• Translation / spellchecking / doc gen
• Other
• I have not used AI

You can read more details in our
Responsible AI Policy

[mtuchi]

This looks good @hunterachieng

[josephjclark]

Is this appropriate for this section of docs?

We're deep in an explanation of state here. I don't think this is the time or place to explain what a cron job is. We could add a single sentence definition, but otherwise we should link to the full cron docs.

Otherwise I think this is just a distraction from the discussion on this page.

[josephjclark]

This feels like the main docs? https://docs.openfn.org/documentation/build/triggers#cron-triggers-formerly-timers

[hunterachieng]

@josephjclark In the link you have shared, the explanation still links to the docs we are currently updating to explain about state in cron jobs.

If readers are being directed to these docs, should we go deeper into state in cron jobs?

[josephjclark]

But that's only for state specifically.

"What is a cron job and how does it work" needs to be answered on build/triggers. I think those docs are fine right now but I'm open to discussing improvements.

"What is the input state passed into my cron job" needs to be explained in-depth in jobs/state. This stuff about "the output of the trigger step will be the input to the next step". It might need a concerete worked example to explain it.

build/triggers can have a single-sentence explanation of how state works, then link to jobs/state for more detail

[hunterachieng]

I have explained more about the state in jobs/state with the new discovery of how state works in cronjobs