What Is A Job?
When you run a workflow, you create a job. Here’s what that means:| What you get | Why it matters |
|---|---|
| Your inputs are saved | You can always see what data you started with |
| Locked workflow version | The job runs exactly the workflow you activated—later edits don’t affect it |
| Results are stored | Access your outputs anytime, even months later |
| Full history | Everything is logged so you can review or audit later |
Jobs are different from Builder previews. Jobs are production runs that are tracked and saved for future reference.
Creating And Running Jobs
From The UI
1
Go to Jobs
Click Jobs in the sidebar, or click New Job from the workflow details page of any active workflow.
2
Pick a workflow
If you started from the Jobs page, select an active workflow from the dropdown. This step is skipped if you started from a workflow details page.
3
Enter your inputs
Fill in the required fields. These match the inputs you defined in your workflow.
For file inputs, you can upload directly or pull from connected integrations. This depends on your workflow design.
4
Run it
Click Execute Job.
5
Watch it run
Track progress in the Jobs dashboard. You can see which steps are running and when they complete.
From The API
You can also start jobs programmatically. This is useful for running jobs on a schedule, automating recurring processes, or triggering workflows from your own applications. See the API Reference for full details.Job Status And Monitoring
Status Indicators
Jobs show clear status indicators as they run:- In Progress: Actively working through the workflow steps
- Completed: Everything finished without errors
- Failed: Something went wrong—you’ll see which step failed and why
Viewing Job Details
On the Job Details page, you can see:- Inputs: What you provided when you started the job
- Outputs: The results (if the job completed)
- Timeline: When each step started and finished
- Errors: What went wrong (if it failed)
- Audit log: The complete record of everything that happened
Error Handling
Common Problems And Fixes
Integration login expired
Integration login expired
What happened: Your connection to an external service (like Google or Slack) expired.Fix: Go to integrations settings, reconnect the service, and re-run the job.Prevent it: Test your integrations in Builder preview before activating.
Rate limit hit
Rate limit hit
What happened: An external API blocked you for making too many requests.Fix: Wait a few minutes and try again.Prevent it: Space out your API calls or process data in smaller batches.
Wrong input type
Wrong input type
What happened: You provided data in the wrong format (like text instead of a number).Fix: Check what type of input the workflow expects and provide the right format.Prevent it: Test your inputs in Builder preview before activating.
Where Errors Appear
Errors are shown in three places on the Job Details page:- On the failed step: The specific step that failed is marked with an error message
- On the job: The overall job shows as Failed with a summary
- In the audit log: Full details for deeper investigation
Jobs And Subworkflows
When your workflow calls another workflow:- The job runs both the main workflow and the sub-workflow
- Both must be active and in the same workspace
- You can see results from both in the job details
Best Practices
Before Running
- Make sure the workflow is active — Draft workflows can’t run jobs
- Test in Builder first — Catch problems before running production jobs
- Check your integrations — Make sure connections haven’t expired
While Running
- Watch for stuck jobs — If a job seems frozen, check for errors
- Don’t run duplicates — Wait for a job to finish before starting another with the same inputs
After Completion
- Check your results — Make sure the outputs look right
- Review failures — Use error details to fix problems in your workflow