At a glance
A run parameter gives a node its value when the tree starts. The editor defines the field and its fallback default; the Hub lets you save the value you want for the next run.
Before you start
Complete setup. This exercise uses Wait in timer-only mode, so it spends no currency. Use a new personal tree and keep bulk off while checking the parameter.
1. Create a timer tree
Press + on the Hub, name the tree Adjustable pause, and open Edit. Add Wait, choose Timer only, and find Wait duration.
Select Run parameter rather than Fixed ms. This changes the source of the duration. Wait durations use milliseconds, so 1000 means one second before any configured timing variation.
2. Create the number field
Open the parameter picker and choose Create new. Use the label Pause milliseconds and a Number field. Select the new parameter for Wait and confirm the node.
Connect Start → Wait → Finish. Each run now reads one duration, waits, then ends. Adding a parameter alone does not affect the flow; the Wait binding is what uses its value.
3. Inspect its setup
Open Params on the editor toolbar to reach Run parameter setup. Find Pause milliseconds and expand Details if needed.
Keep its kind as Run setting (with fallback default). Check that the field is shown on the Start run form and set its Fallback default to 1000. You can also give it a category such as Timing to group it with related fields later.
4. Save a different run value
Return with Back to Hub, expand the tree's Run Parameters, and enter 2000 for Pause milliseconds. Wait for Saved.
In this hypothetical example, the next run uses a two-second main wait. A saved value takes priority over the fallback default. Changing the editor's fallback later will not replace this saved 2000 value.
5. Run and compare
Start the tree and check that it reaches Wait, pauses, and then finishes. Open Logs if you need to confirm which node ran.
After completion, change the saved value to 1000, wait for Saved, and run again. The main wait should be shorter. Change values between runs so the comparison uses a fresh start configuration.
6. Try the fallback deliberately
Clear the saved field and let the change save. With this parameter kind, an empty saved field uses the fallback default at the next start.
Other kinds behave differently: Saved only requires a saved value; Hidden default uses its fallback without a run-form field; Runtime output waits for a node to write it during the run.
Check the result
You should be able to change the main wait using the Hub alone. Reopen Params to confirm the field still binds to Wait and the fallback remains 1000.
If it does not work
- Field is missing: check its kind and Start form option in Params.
- Old duration persists: wait for Saved and start a new run.
- Wait is far too short: enter milliseconds, such as
2000, rather than seconds such as2.