monitor-executions
Skill0 starsChanged 10 months agoMITView on GitHub
Monitor n8n workflow executions. Wait for completion, extract output, get errors, list failed runs. Use for execution tracking and debugging.
In this repository9 other files it gives its agents.
- create-credentialsSkill
- n8n-deploymentSkill
- n8n-diagnosticsSkill
- n8n-patternsSkill
- n8n-securitySkill
- n8n-testingSkill
- test-workflowSkill
- workflow-helpersSkill
- workflow-templatesSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Wait for an execution to finish with polling:
- Distinctive: line 222
Clean Up Old Executions: Delete old failures to save storage
- Distinctive: line 224
Log Execution IDs: Keep audit trail of executions
- Distinctive: line 225
Use Polling Wisely: Don't poll too frequently (1-5 second intervals)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Monitor Executions Skill
This skill provides execution monitoring and data extraction for n8n workflows.
When to Use
- Waiting for workflow execution to complete
- Extracting output data from executions
- Debugging failed executions
- Monitoring execution patterns
- Batch cleanup of old executions
Core Methods
Wait for Completion
Wait for an execution to finish with polling:
const result = await executionHelper.waitForCompletion(
executionId, // Execution ID (number)
60, // Timeout in seconds (default: 60)
1 // Poll interval in seconds (default: 1)
)Result structure:
interface WaitResult {
success: boolean
executionId: string
status: 'success' | 'error' | 'waiting' | 'timeout'
data?: unknown // Output data if successful
error?: string // Error message if failed
duration?: number // Execution duration in seconds
}Extract Output Data
Get output from the last node of an execution:
const output = await executionHelper.getOutput(executionId)Result structure:
interface ExecutionOutput {
success: boolean
data?: unknown // Output data from last node
error?: string
nodeName?: string // Name of the last executed node
}Get Error Message
Extract error message from a failed execution:
const errorMessage = await executionHelper.getError(executionId)
// Returns: string | nullCheck Execution Status
// Check if still running
const running = await executionHelper.isRunning(executionId)
// Returns: boolean
// Get status string
const status = await executionHelper.getStatus(executionId)
// Returns: 'success' | 'error' | 'waiting' | 'unknown'Listing Executions
List Failed Executions
const failures = await executionHelper.listFailed(
workflowId, // Optional: filter by workflow
10 // Limit (default: 10)
)Returns:
Array<{
id: number
workflowId: number
startedAt: string
error?: string
}>List Running Executions
const running = await executionHelper.listRunning(
workflowId, // Optional: filter by workflow
10 // Limit (default: 10)
)Returns:
Array<{
id: number
workflowId: number
startedAt: string
}>Batch Operations
Delete Multiple Executions
const result = await executionHelper.deleteMany({
workflowId: 'xxx', // Optional: filter by workflow
status: 'error', // Optional: 'error' | 'success' | 'waiting'
limit: 100 // Max to delete (default: 100)
})Returns:
interface BatchDeleteResult {
success: boolean
deletedCount?: number
error?: string
}Usage Examples
Complete Execution Workflow
// Start workflow execution (via webhook or other trigger)
const executionId = startWorkflow()
// Wait for completion
const result = await executionHelper.waitForCompletion(executionId, 120)
if (result.status === 'success') {
console.log('Workflow completed successfully')
console.log('Output:', result.data)
console.log('Duration:', result.duration, 'seconds')
} else if (result.status === 'error') {
console.error('Workflow failed:', result.error)
// Get more details
const fullError = await executionHelper.getError(executionId)
} else if (result.status === 'timeout') {
console.warn('Workflow still running after timeout')
// Execution continues in background
}Debug Recent Failures
// Get last 5 failures
const failures = await executionHelper.listFailed(workflowId, 5)
for (const failure of failures) {
console.log(`Execution ${failure.id} failed at ${failure.startedAt}`)
// Get detailed error
const error = await executionHelper.getError(failure.id)
console.log('Error:', error)
// Get output to see what data was processed
const output = await executionHelper.getOutput(failure.id)
console.log('Last node:', output.nodeName)
console.log('Data:', output.data)
}Cleanup Old Executions
// Delete all failed executions older than limit
const cleaned = await executionHelper.deleteMany({
status: 'error',
limit: 1000
})
if (cleaned.success) {
console.log(`Deleted ${cleaned.deletedCount} failed executions`)
}Monitor Running Executions
// Check for stuck executions
const running = await executionHelper.listRunning()
for (const exec of running) {
const startTime = new Date(exec.startedAt)
const runningTime = (Date.now() - startTime.getTime()) / 1000
if (runningTime > 3600) { // Running for over an hour
console.warn(`Execution ${exec.id} running for ${runningTime}s - may be stuck`)
}
}Best Practices
- Set Appropriate Timeouts: Match timeout to expected execution time
- Handle All Status Cases: success, error, timeout, waiting
- Clean Up Old Executions: Delete old failures to save storage
- Monitor Patterns: Track failure rates over time
- Log Execution IDs: Keep audit trail of executions
- Use Polling Wisely: Don't poll too frequently (1-5 second intervals)
Common Issues
Execution Not Found
- Execution was deleted
- Wrong execution ID
- Execution hasn't started yet
Timeout Without Completion
- Workflow takes longer than expected
- Workflow is stuck/infinite loop
- External service is slow
No Output Data
- Workflow has no nodes
- Last node produced no output
- Execution failed before output node
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

