n8n - 💡(How to fix) Fix webhook trigger's workflow can not be activated [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#28285Fetched 2026-04-11 06:30:59
View on GitHub
Comments
2
Participants
3
Timeline
5
Reactions
0
Author
Timeline (top)
commented ×2labeled ×1mentioned ×1subscribed ×1

Error Message

it reports 'The workflow has been activated but cannot be started.Click to display the error message.' The workflow has been activated but cannot be started.Click to display the error message.

RAW_BUFFERClick to expand / collapse

Bug Description

my workflow has only one webhook node, but it cannot be activated.

<img width="515" height="433" alt="Image" src="https://github.com/user-attachments/assets/2c672f1a-523e-4381-93fe-65fffa30ccea" />

it reports 'The workflow has been activated but cannot be started.Click to display the error message.'

<!-- Failed to upload "image.png" -->

but nothing display when I Click.

To Reproduce

v2.15.0

  1. add workflow
  2. add webhook node, keep default setings
  3. try to activiate it

Expected behavior

workflow activiated successfully

Debug Info

The workflow has been activated but cannot be started.Click to display the error message.

Operating System

docker

n8n Version

v2.15.0

Node.js Version

docker

Database

PostgreSql

Execution mode

main (default)

Hosting

n8n cloud

extent analysis

TL;DR

Check the workflow and webhook node configuration for potential issues that might be preventing the workflow from starting.

Guidance

  • Verify that the webhook node is properly configured and that its default settings are correct for the specific use case.
  • Check the n8n cloud logs for any error messages that might provide more information about why the workflow cannot be started.
  • Ensure that the PostgreSql database is properly connected and configured for the n8n workflow.
  • Try to activate the workflow in a local environment to see if the issue is specific to the n8n cloud hosting.

Example

No code snippet is provided as the issue does not contain enough information to create a relevant example.

Notes

The issue might be related to a specific configuration or setup in the n8n cloud or PostgreSql database, and more information about the error message or logs would be helpful to provide a more accurate solution.

Recommendation

Apply workaround: Try to activate the workflow in a local environment to isolate the issue and see if it's specific to the n8n cloud hosting, as this can help to identify if the problem is with the workflow configuration or the hosting environment.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

workflow activiated successfully

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING