fix(FN-1028): add crypto.randomUUID fallback for schedule step ID generation

- Add fallback ID generation using Math.random when crypto.randomUUID is unavailable
- Update ScheduleStepsEditor component with robust step creation
- Add unit tests for fallback ID generation behavior
- Document fallback approach in Scheduled Tasks section of README
This commit is contained in:
gsxdsm
2026-04-06 00:09:21 -07:00
parent 2eae2834f4
commit 76770e6e14
3 changed files with 56 additions and 2 deletions

View File

@@ -595,7 +595,7 @@ Automate recurring workflows with multi-step scheduled tasks:
| `weekly` | `0 0 * * 0` | Weekly on Sunday |
| `custom` | — | Define your own cron |
Each schedule contains multiple steps executed sequentially. Steps can be commands (with timeout and `continueOnFailure` options) or AI prompts. Access via the **Scheduled Tasks** button in the dashboard header.
Each schedule contains multiple steps executed sequentially. Steps can be commands (with timeout and `continueOnFailure` options) or AI prompts. Step creation works in all browser environments, including non-secure contexts (HTTP) where `crypto.randomUUID()` is unavailable, via deterministic fallback ID generation. Access via the **Scheduled Tasks** button in the dashboard header.
## Development