Using a workflow: save, run and stop are different steps
Redaily
3/21/2025
Updated
Saving a workflow stores configuration; it does not prove execution has started. Schedules must also be saved and depend on a working local browser. Distinguishing these states helps prevent duplicate runs.
Create and name a plan, review its targets, actions and filters, then save. Start once and observe the task tab. Stop when needed and wait for the state change. Check the start, end and result in the log.
Save again after configuration changes. Old logs reflect old conditions and should not be interpreted as if they used your new settings.
Visible evidence for three states
| State | Expected evidence | Not established |
|---|---|---|
| Saved | Plan/configuration can be reopened | Execution has started |
| Running | Matching state and page activity | Every target will succeed |
| Stopped/finished | State change and run record | Published actions were undone |
Verify after a change
After changing a keyword, save and reopen configuration. Do not explain a still-running older plan with new settings. Record what changed, why and which run will test it.
For no apparent response, inspect saved state, execution state, page opening, login and logs in sequence. Repeated starts confuse the evidence, while a reset can erase it.
Product reference
Product steps were checked against extension 3.5.3. See the related guide for instructions and pricing for access. Report behavior that differs through feedback, including the version and a redacted error.
