Analyzing executions?

[toobulkeh]

Hey there, I’m new to n8n and exploring how it’ll help us scale! Love what I see so far.
What I’d love to learn more about is how can I see execution data?

Describe the problem/error/question

I can see a list of recent executions and their status, and I can rerun failed ones, but can I get any more details about it?

For example I turned on a webhook trigger and it’s executing every minute, though I expected it to be once a day or so. I did move it from my personal workspace to a shared workspace and didn’t realize that didn’t move the credentials with it, so it stopped working. Over the course of a week it blew through all the free tier credits, but I’m not sure why.

So I’d like to triage what is the data it’s receiving so frequently, or if something else is causing it to rerun?

What is the error message (if any)?

No error messages

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

• n8n version: 1.79.2
• Database (default: SQLite): cloud
• n8n EXECUTIONS_PROCESS setting (default: own, main): own
• Running n8n via n8n cloud
• Operating system: N/A

instance information

Debug info

core

• n8nVersion: 1.79.2
• platform: docker (cloud)
• nodeJsVersion: 20.18.2
• database: sqlite
• executionMode: regular
• concurrency: 5
• license: community
• consumerId: 00000000-0000-0000-0000-000000000000

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: filesystem

pruning

• enabled: true
• maxAge: 168 hours
• maxCount: 2500 executions

client

• userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/133.0.0.0 safari/537.36
• isTouchDevice: false

Generated at: 2025-02-21T00:51:21.642Z

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[bartv]

Are you logging succesful executions? Depending on your instance settings, you may have to change the workflow settings to do so:

After this, you can inspect the execution data by double-clicking any node in a past execution. I also recommend registering your instance to get access to some additional features including ‘debugging to editor’ which lets you copy the values of previous executions to the editor for debugging.

[toobulkeh]

We’re on the cloud version, so those were already turned on.

How do you debugging to editor? Maybe I’m just missing the UI steps I need to use.

Thanks!

[bartv]

You’ll find it at the top-right of the screen when you’re looking at an execution. For failed executions it will be labeled ‘Debug in Editor’:

[toobulkeh]

Hmm, so clicking “Copy to editor” opens up the editor view and I see the nodes. I don’t see any data though. Clicking into a node I then see the usual “Listen for test event” buttons, but no data of that execution.

“Debug in Editor” is the same thing, except it shows me an error message. Still no data.

Maybe this is a feature request? It would be great to be able to see the data at each step!

[bartv]

There should be data in your webhook node? If not, it didn’t receive anything.

[toobulkeh]

Weird, I was clicking those nodes and not seeing anything, but now going back and reviewing I can see it now. Not sure what wasn’t working.

I was also expecting it to be on the left side of the node, not the right side (since I wanted to see a webhook input) so that was a bit confusing.

That said, It would still be great to see this in a table format or something more of a log report instead of having to click into each execution and each node!

Either way, that answered it. Thanks!