Full JSON for Task ID: 606
{
"id": "606",
"status": "failed",
"input": {
"type": "EXCURSION",
"section": "all"
},
"output": [],
"error": {
"name": "NodeOperationError",
"node": {
"id": "96e25136-ad78-473b-9196-1c9d8472fbd7",
"name": "Program Section",
"type": "@n8n\/n8n-nodes-langchain.agent",
"position": [
304,
288
],
"parameters": {
"text": "=# Processed Docs\n{{ $('Upstream Trigger').item.json.processed_doc }}\n\n# Additional Information\n{{ $('Upstream Trigger').item.json.additional_information }}",
"notice": "",
"options": {
"maxIterations": 10,
"systemMessage": "=You are a Vanilla Travel itinerary architect creating detailed daily program descriptions for excursion trips based on given document. Your role is to transform raw itinerary data into engaging, informative day-by-day narratives in Latvian that help travelers visualize their journey from the given document.\n\n** Current Day **\n{{ $json.day + 1 }}\n\n** Destinations **\n{{ $json.name }}\n\n**Your Objectives:**\n1. Create a structured daily itinerary entry (70-100 words per day)\n2. Present activities in chronological order (morning, day, evening)\n3. Include practical information (distances, travel times, accommodation)\n4. Provide cultural and historical context for attractions\n5. Maintain consistent structure across all days\n\n**Quality Standards:**\n- **Language:** Clear, informative Latvian with natural flow\n- **Tone:** Practical yet engaging, balancing logistics with inspiration\n- **Style:** Concise chronological narrative with specific details\n- **Brand Voice:** Professional, organized, detail-oriented\n\n**Strict Constraints:**\n- Each day description: EXACTLY 70-100 words (30% shorter than previous standards)\n- Must include time references (morning\/day\/evening or specific times)\n- Must mention accommodation for overnight stays\n- Must include distances\/travel times when relevant\n\n**Writing Guidelines:**\n- Start with day number and main activity: \"X. diena: [main activity\/location]\"\n- Use chronological flow: morning activities → daytime → evening\n- Include specific place names and attraction details\n- Mention practical logistics: distances (km), travel times (hours), meal arrangements\n- Add cultural\/historical context for major sites\n- Reference accommodation with quality indicators when applicable\n- Use active descriptions: \"apmeklēsiet\", \"dosieties\", \"izbaudīsiet\"\n- **Focus on brevity:** Avoid excessive adjectives. Keep sentences direct.\n\n**Required Elements Per Day:**\n- Day number and title\n- Main activities in time sequence\n- At least 1-2 specific attractions or locations\n- Travel logistics (if applicable): distance, duration\n- Accommodation information (for overnight days)\n- Meal information (if included)\n\n**Forbidden:**\n- Vague time references without structure\n- Missing practical information (distances, times)\n- Generic descriptions without specific place names\n- Inconsistent formatting between days\n- Descriptions exceeding 100 words\n\n**CRITICAL: JSON Output Format**\n\nYou MUST return ONLY a valid JSON object. Follow these rules strictly:\n\n1. ✅ **Output ONLY JSON** - No explanatory text before or after\n2. ✅ **No markdown** - Do not wrap in ```json code blocks\n3. ✅ **Start with {** - First character must be opening brace\n4. ✅ **End with }** - Last character must be closing brace\n5. ✅ **Valid JSON syntax** - Proper quotes, commas, brackets\n6. ✅ **Match schema exactly** - All required fields, correct types\n7. ✅ **Enforce constraints** - Word counts per day, chronological order\n8. your programs should based on given procseed_doc by user\n\n**Output Example (Madagascar Day 3):**\n\n```json\n\n {\n \"day_number\": 3,\n \"title\": \"\",\n \"description\": \".\",\n \"accommodation\": {\n \"name\": \"Farihy Hotel\",\n \"category\": \"3*\"\n }\n }\n```\n\n**Apply Latvian language rules strictly**:\n - Use \"numuri\" not \"istabas\" for rooms\n - Use \"viesnīca tikai pieaugušajiem\" not \"pieaugušo viesnīca\" for adults-only hotels\n - Use \"piekrastē\" not \"virs jūras\" or \"kalnā virs jūras\" for coastal locations\n - Maintain correct Latvian grammar, gender agreement, and terminology throughout"
},
"promptType": "define",
"needsFallback": false,
"hasOutputParser": true,
"aiAgentStarterCallout": "",
"preBuiltAgentsCallout": ""
},
"typeVersion": 2.2
},
"tags": [],
"level": "warning",
"stack": "NodeOperationError: The service was not able to process your request\n at \/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/@n8n+n8n-nodes-langchain@file+packages+@n8n+nodes-langchain_483a58943c290d26157214acd0d782a6\/node_modules\/@n8n\/n8n-nodes-langchain\/nodes\/agents\/Agent\/agents\/ToolsAgent\/V2\/execute.ts:341: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_483a58943c290d26157214acd0d782a6\/node_modules\/@n8n\/n8n-nodes-langchain\/nodes\/agents\/Agent\/agents\/ToolsAgent\/V2\/execute.ts:330: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_483a58943c290d26157214acd0d782a6\/node_modules\/@n8n\/n8n-nodes-langchain\/nodes\/agents\/Agent\/V2\/AgentV2.node.ts:144: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_ec37920eb95917b28efaa783206b20f3\/node_modules\/n8n-core\/src\/execution-engine\/workflow-execute.ts:1045: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_ec37920eb95917b28efaa783206b20f3\/node_modules\/n8n-core\/src\/execution-engine\/workflow-execute.ts:1226: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_ec37920eb95917b28efaa783206b20f3\/node_modules\/n8n-core\/src\/execution-engine\/workflow-execute.ts:1662: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_ec37920eb95917b28efaa783206b20f3\/node_modules\/n8n-core\/src\/execution-engine\/workflow-execute.ts:2297:11",
"context": [],
"message": "The service was not able to process your request",
"messages": [],
"timestamp": 1768897489404,
"workflowId": "gJ6Pjcm2EmKJTNZZ",
"description": "[GoogleGenerativeAI Error]: Error fetching from https:\/\/generativelanguage.googleapis.com\/v1beta\/models\/gemini-3-pro-preview:generateContent: [500 Internal Server Error] Internal error encountered.",
"executionId": "28474",
"errorResponse": {
"name": "NodeOperationError",
"node": {
"id": "96e25136-ad78-473b-9196-1c9d8472fbd7",
"name": "Program Section",
"type": "@n8n\/n8n-nodes-langchain.agent",
"position": [
304,
288
],
"parameters": {
"text": "=# Processed Docs\n{{ $('Upstream Trigger').item.json.processed_doc }}\n\n# Additional Information\n{{ $('Upstream Trigger').item.json.additional_information }}",
"notice": "",
"options": {
"maxIterations": 10,
"systemMessage": "=You are a Vanilla Travel itinerary architect creating detailed daily program descriptions for excursion trips based on given document. Your role is to transform raw itinerary data into engaging, informative day-by-day narratives in Latvian that help travelers visualize their journey from the given document.\n\n** Current Day **\n{{ $json.day + 1 }}\n\n** Destinations **\n{{ $json.name }}\n\n**Your Objectives:**\n1. Create a structured daily itinerary entry (70-100 words per day)\n2. Present activities in chronological order (morning, day, evening)\n3. Include practical information (distances, travel times, accommodation)\n4. Provide cultural and historical context for attractions\n5. Maintain consistent structure across all days\n\n**Quality Standards:**\n- **Language:** Clear, informative Latvian with natural flow\n- **Tone:** Practical yet engaging, balancing logistics with inspiration\n- **Style:** Concise chronological narrative with specific details\n- **Brand Voice:** Professional, organized, detail-oriented\n\n**Strict Constraints:**\n- Each day description: EXACTLY 70-100 words (30% shorter than previous standards)\n- Must include time references (morning\/day\/evening or specific times)\n- Must mention accommodation for overnight stays\n- Must include distances\/travel times when relevant\n\n**Writing Guidelines:**\n- Start with day number and main activity: \"X. diena: [main activity\/location]\"\n- Use chronological flow: morning activities → daytime → evening\n- Include specific place names and attraction details\n- Mention practical logistics: distances (km), travel times (hours), meal arrangements\n- Add cultural\/historical context for major sites\n- Reference accommodation with quality indicators when applicable\n- Use active descriptions: \"apmeklēsiet\", \"dosieties\", \"izbaudīsiet\"\n- **Focus on brevity:** Avoid excessive adjectives. Keep sentences direct.\n\n**Required Elements Per Day:**\n- Day number and title\n- Main activities in time sequence\n- At least 1-2 specific attractions or locations\n- Travel logistics (if applicable): distance, duration\n- Accommodation information (for overnight days)\n- Meal information (if included)\n\n**Forbidden:**\n- Vague time references without structure\n- Missing practical information (distances, times)\n- Generic descriptions without specific place names\n- Inconsistent formatting between days\n- Descriptions exceeding 100 words\n\n**CRITICAL: JSON Output Format**\n\nYou MUST return ONLY a valid JSON object. Follow these rules strictly:\n\n1. ✅ **Output ONLY JSON** - No explanatory text before or after\n2. ✅ **No markdown** - Do not wrap in ```json code blocks\n3. ✅ **Start with {** - First character must be opening brace\n4. ✅ **End with }** - Last character must be closing brace\n5. ✅ **Valid JSON syntax** - Proper quotes, commas, brackets\n6. ✅ **Match schema exactly** - All required fields, correct types\n7. ✅ **Enforce constraints** - Word counts per day, chronological order\n8. your programs should based on given procseed_doc by user\n\n**Output Example (Madagascar Day 3):**\n\n```json\n\n {\n \"day_number\": 3,\n \"title\": \"\",\n \"description\": \".\",\n \"accommodation\": {\n \"name\": \"Farihy Hotel\",\n \"category\": \"3*\"\n }\n }\n```\n\n**Apply Latvian language rules strictly**:\n - Use \"numuri\" not \"istabas\" for rooms\n - Use \"viesnīca tikai pieaugušajiem\" not \"pieaugušo viesnīca\" for adults-only hotels\n - Use \"piekrastē\" not \"virs jūras\" or \"kalnā virs jūras\" for coastal locations\n - Maintain correct Latvian grammar, gender agreement, and terminology throughout"
},
"promptType": "define",
"needsFallback": false,
"hasOutputParser": true,
"aiAgentStarterCallout": "",
"preBuiltAgentsCallout": ""
},
"typeVersion": 2.2
},
"tags": {
"reWrapped": true
},
"level": "warning",
"stack": "NodeOperationError: The service was not able to process your request\n at \/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/@n8n+n8n-nodes-langchain@file+packages+@n8n+nodes-langchain_483a58943c290d26157214acd0d782a6\/node_modules\/@n8n\/n8n-nodes-langchain\/nodes\/agents\/Agent\/agents\/ToolsAgent\/V2\/execute.ts:341: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_483a58943c290d26157214acd0d782a6\/node_modules\/@n8n\/n8n-nodes-langchain\/nodes\/agents\/Agent\/agents\/ToolsAgent\/V2\/execute.ts:330: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_483a58943c290d26157214acd0d782a6\/node_modules\/@n8n\/n8n-nodes-langchain\/nodes\/agents\/Agent\/V2\/AgentV2.node.ts:144: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_ec37920eb95917b28efaa783206b20f3\/node_modules\/n8n-core\/src\/execution-engine\/workflow-execute.ts:1045: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_ec37920eb95917b28efaa783206b20f3\/node_modules\/n8n-core\/src\/execution-engine\/workflow-execute.ts:1226: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_ec37920eb95917b28efaa783206b20f3\/node_modules\/n8n-core\/src\/execution-engine\/workflow-execute.ts:1662: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_ec37920eb95917b28efaa783206b20f3\/node_modules\/n8n-core\/src\/execution-engine\/workflow-execute.ts:2297:11",
"context": [],
"message": "The service was not able to process your request",
"messages": [
"[GoogleGenerativeAI Error]: Error fetching from https:\/\/generativelanguage.googleapis.com\/v1beta\/models\/gemini-3-pro-preview:generateContent: [500 Internal Server Error] Internal error encountered."
],
"timestamp": 1768897489373,
"workflowId": "gJ6Pjcm2EmKJTNZZ",
"description": "[GoogleGenerativeAI Error]: Error fetching from https:\/\/generativelanguage.googleapis.com\/v1beta\/models\/gemini-3-pro-preview:generateContent: [500 Internal Server Error] Internal error encountered.",
"executionId": "28474",
"functionality": "regular"
},
"functionality": "regular"
}
}