You built a workflow and nothing happens. Check these in order.
1. Is it active?
Production triggers run only for active workflows. The Manual trigger never runs by itself.
2. Is n8n running?
A stopped container, sleeping laptop or crashed server cannot run schedules.
3. Test vs production
You may be using the test webhook URL (test vs production).
4. Schedule and time zone
Check the interval and time zone (schedule trigger).
5. App trigger problems
Credentials may have expired, permissions may be missing or the app may limit how often it checks.
6. Check executions
Open the executions list. If runs exist but failed, read the error: debugging executions.
7. Public address
For webhooks, the sender must reach your server. See webhook 404.
Quick answers
Why is my workflow not starting?
It may be inactive, n8n may be stopped or you may use the test URL.
Where do I look first?
The executions list.
Do schedules run when my laptop sleeps?
No, n8n must be running.
Related reading
- n8n Webhook Returning 404 or Not Working: How to Fix It
- How to Handle Errors in n8n with an Error Workflow
- How to Debug n8n Executions and Data Problems
Not sure where to start?
Tell us your goal, whether it is your own business, freelancing, studies or a job, and we will say honestly if our 15-day live n8n course is the right fit.
See the 15-day n8n training | Find your city | Book free counselling