RumataWorkflow trigger and schedule controls
Choose how a workflow starts, define its HTTP route, manage a server schedule, and control execution history.
Step-by-step guidance.
Before you start
- Open the named screen in Rumata. Available controls may depend on your account, permissions, and resource state.
HTTP and manual starts
Select the trigger step on the canvas. Trigger edits take effect when the workflow is saved.
| Control | What it does |
|---|---|
| How it starts | Choose an incoming HTTP request, a manual run, or a schedule. |
| Method | Choose the HTTP action callers must use, such as GET to retrieve information or POST to submit data. |
| URL path | Set the route, such as /orders/:id. The callable address is shown below. Without a path the workflow can still run by its ID. |
| Response → Wait for result | Keep the request open until the workflow returns its final output. |
| Response → Return run ID | Respond with a run identifier so a longer workflow can continue in the background. |
| Connector trigger setup hint | Read the selected service’s webhook setup instructions and copy its displayed URL into that service as directed. Saving the workflow is required to activate its route. |
Schedule settings and live activation
Saved schedules run on the server while Studio is closed. Choose Save to apply draft changes to the schedule’s frequency. The Schedule active switch changes the saved schedule immediately.
| Control | What it does |
|---|---|
| Schedule active | Pause or resume the saved schedule now. Pausing prevents new scheduled starts; it does not rewrite its cadence. |
| Schedule by | Choose Every N seconds, Calendar, or Cron expression. |
| Run every (seconds) | Set the interval between scheduled starts. |
| Time of day | Choose the calendar start time. The screen names the browser timezone it uses. |
| Weekday buttons | Select the days to run. With no days selected, the schedule runs every day. |
| Cron expression | Enter a technical schedule expression. For everyday schedules, Calendar or an interval is easier to use. |
| Schedule status help | Explain Active, Paused, or Not scheduled yet. An unsaved workflow must be saved to create its server schedule. |
Execution engine and retained data
Most workflows can keep Auto. Durable execution supports work that must wait or recover; eligible simple synchronous workflows can use the lower-latency fast path.
| Control | What it does |
|---|---|
| Execution engine → Auto / Fast / Durable | Choose an execution preference. Read the eligibility explanation beneath it; Fast can fall back to Durable when the graph is not eligible. |
| Save fast-path step details | Retain per-step inputs, outputs, and timings for fast runs. It starts off; basic run status and response time are recorded separately. |
| Run history data → Keep step data | Keep large step inputs, outputs, and results available for later inspection. |
| Run history data → Delete large temporary data after each run | Remove large temporary values after completion. Status, errors, timings, small values, and files explicitly saved by the workflow remain. |