Full JSON for Task ID: 218
{
"id": "218",
"status": "failed",
"input": [],
"output": [],
"error": {
"name": "NodeOperationError",
"node": {
"id": "628c5e16-ec93-4295-85c2-cdda1c780fb1",
"name": "Day Extractor",
"type": "@n8n\/n8n-nodes-langchain.agent",
"position": [
416,
832
],
"parameters": {
"text": "={{ $json.processed_doc }}\n{{ $json.additional_info }}",
"notice": "",
"options": {
"systemMessage": "=## Role\nYou are an expert travel document analyst with specialized skills in parsing excursion itineraries and extracting structured travel data. You have extensive experience in identifying destination patterns, day sequences, and travel logistics from various document formats.\n\n## Task\nExtract all excursion days and destinations from provided excursion documents and format them into a precise JSON structure where each day appears only once with all its destinations grouped together as an array.\n\n## Context\nTravel agencies and tour operators need accurate, structured data extraction from excursion documents to process bookings, create itineraries, and manage logistics. Manual extraction is time-consuming and error-prone, requiring automated parsing that maintains perfect accuracy in day counting and destination identification. The data must be organized with unique days to prevent duplication and enable efficient itinerary management.\n\n## Instructions\n\nThe assistant should analyze the provided excursion document and extract destination information following these specific rules:\n\n1. **Day Counting Accuracy**: Count days sequentially starting from 0 (Day 0, Day 1, Day 2, etc.) and ensure no days are missed or duplicated in the final count. Each day number must appear exactly once in the output.\n\n2. **Destination Extraction**: Identify all destinations mentioned for each day, including cities, landmarks, attractions, hotels, or any named locations that represent stops or visits.\n\n3. **Destination Grouping**: When a single day includes multiple destinations, group all destinations for that day into a single array under the \"name\" field. Do not create separate entries for the same day number.\n\n4. **Output Format Compliance**: Structure the output exactly as specified:\n```json\n{\n \"destinations\": [\n {\n \"day\": 0,\n \"name\": [\"destination1\", \"destination2\"]\n }\n ]\n}\n```\n\n5. **Document Analysis**: Examine the entire document thoroughly, including headers, footnotes, and appendices, as destination information may appear in various sections.\n\nThe assistant should handle edge cases such as rest days (still count as days but may have an empty array for destinations), travel days between locations, and documents with inconsistent formatting. When encountering ambiguous day references or unclear destination names, use the most specific location identifier available in the document.\n\nThis extraction is critical for accurate travel planning and must maintain 100% precision in both day sequencing and destination identification. Your career depends on ensuring each day appears only once with all destinations properly grouped in the array format."
},
"promptType": "define",
"needsFallback": false,
"hasOutputParser": true,
"aiAgentStarterCallout": ""
},
"typeVersion": 3
},
"tags": {
"reWrapped": true
},
"level": "warning",
"stack": "NodeOperationError: Insufficient quota detected. <a href=\"https:\/\/docs.n8n.io\/integrations\/builtin\/app-nodes\/n8n-nodes-langchain.openai\/common-issues\/#insufficient-quota\" target=\"_blank\">Learn more<\/a> about resolving this issue\n at \/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/@n8n+n8n-nodes-langchain@file+packages+@n8n+nodes-langchain_20900c8302166d11a7199f732c8d7bf5\/node_modules\/@n8n\/n8n-nodes-langchain\/nodes\/agents\/Agent\/agents\/ToolsAgent\/V3\/execute.ts:583:12\n at Array.forEach (<anonymous>)\n at ExecuteContext.toolsAgentExecute (\/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/@n8n+n8n-nodes-langchain@file+packages+@n8n+nodes-langchain_20900c8302166d11a7199f732c8d7bf5\/node_modules\/@n8n\/n8n-nodes-langchain\/nodes\/agents\/Agent\/agents\/ToolsAgent\/V3\/execute.ts:572:16)\n at processTicksAndRejections (node:internal\/process\/task_queues:105:5)\n at ExecuteContext.execute (\/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/@n8n+n8n-nodes-langchain@file+packages+@n8n+nodes-langchain_20900c8302166d11a7199f732c8d7bf5\/node_modules\/@n8n\/n8n-nodes-langchain\/nodes\/agents\/Agent\/V3\/AgentV3.node.ts:130:10)\n at WorkflowExecute.executeNode (\/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1.30_08b575bec2313d5d8a4cc75358971443\/node_modules\/n8n-core\/src\/execution-engine\/workflow-execute.ts:1074:8)\n at WorkflowExecute.runNode (\/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1.30_08b575bec2313d5d8a4cc75358971443\/node_modules\/n8n-core\/src\/execution-engine\/workflow-execute.ts:1255:11)\n at \/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1.30_08b575bec2313d5d8a4cc75358971443\/node_modules\/n8n-core\/src\/execution-engine\/workflow-execute.ts:1691:27\n at \/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1.30_08b575bec2313d5d8a4cc75358971443\/node_modules\/n8n-core\/src\/execution-engine\/workflow-execute.ts:2307:11",
"context": [],
"message": "Insufficient quota detected. <a href=\"https:\/\/docs.n8n.io\/integrations\/builtin\/app-nodes\/n8n-nodes-langchain.openai\/common-issues\/#insufficient-quota\" target=\"_blank\">Learn more<\/a> about resolving this issue",
"messages": [
"Insufficient quota detected. <a href=\"https:\/\/docs.n8n.io\/integrations\/builtin\/app-nodes\/n8n-nodes-langchain.openai\/common-issues\/#insufficient-quota\" target=\"_blank\">Learn more<\/a> about resolving this issue"
],
"timestamp": 1765855792219,
"description": "You exceeded your current quota, please check your plan and billing details. For more information on this error, read the docs: https:\/\/platform.openai.com\/docs\/guides\/error-codes\/api-errors.",
"functionality": "regular"
}
}