Skip to main content
The Workflows tab in the editor gives you visibility into all registered workflows — execution history, errors, and status.

​
Viewing your workflows

Open the Workflows tab to see all registered workflows. Each entry displays:
DetailDescription
NameThe function name and ID
ScheduleThe cron expression (for scheduled jobs) or event trigger (for event-driven functions)
Recent executionsA summary of recent runs with status indicators

​
Execution history and logs

Each workflow tracks its execution history with three statuses:
  • Success — All steps completed without errors
  • Failure — One or more steps failed after all retry attempts
  • Running — Currently executing
Click on a specific execution to see detailed logs: which steps ran, timing information, and error messages with stack traces for failed steps.

​
Testing during development

Workflows are synced to your sandbox environment, so you can test them before deploying to production. Scheduled workflows execute on their defined schedule within the sandbox, and event-driven workflows trigger when your sandbox app emits the relevant event.
To test a scheduled workflow without waiting for the next cron tick, ask the AI to trigger it manually or temporarily set the schedule to every minute.

​
Deploying workflows

Workflows are deployed as part of your app — no separate deployment needed. When you click Deploy, Vybe:
  1. Registers your workflow functions with Inngest
  2. Activates cron schedules on the production environment
  3. Starts event listeners for event-driven functions

​
Disabling workflows

Two options to stop a workflow:
  • From the Workflows tab — Disable it directly from the UI. Takes effect immediately without removing the code.
  • From the code — Ask the AI to remove the workflow function. Takes effect on the next deployment.
Disabling a workflow does not delete its execution history. You can still view past runs and logs.

​
Troubleshooting

If your workflows are not running as expected, check these common issues:
Ensure the workflow function is properly exported and registered in your Inngest configuration. The AI handles this automatically, but if you edited code manually, verify the wiring.
Cron schedules use UTC time. Check the cron expression and account for the timezone difference. Ask the AI to adjust the schedule.
Individual steps have execution time limits. Break long-running operations into smaller steps or optimize them to complete faster.
The event name in your inngest.send() call must match the event name in the workflow’s trigger configuration exactly.

​
What’s next