# Scheduling & Running Workflows

Once you've built a workflow, you can run it on demand or set it up to execute automatically on a schedule. This guide covers both approaches and how to monitor workflow execution.

# Running a Workflow Manually

1. Open a workflow from the Workflows tab in the sidebar
2. Click the Play button in the toolbar (the green circle with a play icon)
3. The button changes to a spinning progress indicator while the workflow executes
4. When finished, a status icon appears:
   • Green checkmark — The workflow completed successfully
   • Orange warning — The workflow encountered an issue

If the workflow includes an Ask for Input node, a prompt will appear during execution for you to provide input before it continues.

# Scheduling a Workflow

To run a workflow automatically:

1. Click the Trigger node in the workflow editor
2. In the config panel, change the trigger type from Manual to Scheduled
3. Choose an interval:
   • Every X minutes — Runs at a fixed minute interval
   • Hourly — Runs once per hour
   • Daily — Runs once per day
   • Weekly — Runs once per week
4. Save the workflow

Scheduled workflows run automatically while Weavestream is open. If the app is closed during a scheduled time, the workflow will run at the next opportunity when the app is opened.

Note: Workflows with Ask for Input nodes aren't ideal for scheduled execution, since they require manual interaction. Consider using Condition or Filter nodes instead for fully automated workflows.

# Viewing Run Logs

After a workflow has been run at least once, the Run Log button appears in the toolbar (the document icon). Click it to see details about the most recent execution:

# Run Summary

• Status — Whether the run succeeded or encountered errors
• Duration — How long the entire workflow took to execute
• Node name — Which workflow was run

# Execution Log

A timestamped log shows what happened at each step:

• Which nodes were executed and in what order
• Data passed between nodes
• Any messages or outputs generated
• Timestamps for each step

# Errors

If any nodes failed during execution, the error section shows what went wrong. This is helpful for debugging issues with API connections, AI analysis, or notification delivery.

Click Done to close the run log.

# Workflow States

A workflow can be in one of these states:

# Saving Workflows

Workflows are saved to your Mac's local storage. Changes are not saved automatically — you need to click Save (or press Cmd+S) after making edits. An indicator in the toolbar shows when you have unsaved changes.

# Tips

• Test before scheduling. Run a workflow manually first to make sure it works as expected. Then set up the schedule.
• Check run logs regularly. Scheduled workflows run in the background. Review the logs periodically to make sure everything is working.
• Keep workflows focused. A workflow that does one thing well is easier to debug than one that tries to do everything. Create multiple workflows for different tasks.
• Use conditions for error handling. Add Condition nodes to handle cases where data is empty or unexpected. For example, only send a notification if the item count is greater than zero.

# Next Steps

• Workflow Node Reference — Detailed reference for all node types
• Building Your First Workflow — Step-by-step tutorial
• Notifications Settings — Configure notification permissions