Telegram Node "Get a File"
Get File Node uses the File id from Telegram Trigger Node so this is type of parameter passing Run ID : fca98d76-ecc0-4a86-a350-44e4d8a1867f Indie : n8n : File :
Mathesh Natarajan 4 days ago
🐛 Bug Reports
Telegram Node "Get a File"
Get File Node uses the File id from Telegram Trigger Node so this is type of parameter passing Run ID : fca98d76-ecc0-4a86-a350-44e4d8a1867f Indie : n8n : File :
Mathesh Natarajan 4 days ago
🐛 Bug Reports
Completed
Telegram Get File node fails with 404 resource not found
Telegram “Get a file” node fails during execution with a 404 error stating the requested resource could not be found. File:
Mathesh Natarajan 5 days ago
🐛 Bug Reports
Completed
Telegram Get File node fails with 404 resource not found
Telegram “Get a file” node fails during execution with a 404 error stating the requested resource could not be found. File:
Mathesh Natarajan 5 days ago
🐛 Bug Reports
Completed
Unable to bring workflow live due to service data not found error
Workflow cannot be set to live and shows “Service data not found for contract” error, blocking activation.
Mathesh Natarajan 5 days ago
🐛 Bug Reports
Completed
Unable to bring workflow live due to service data not found error
Workflow cannot be set to live and shows “Service data not found for contract” error, blocking activation.
Mathesh Natarajan 5 days ago
🐛 Bug Reports
Completed
Telegram Get File node fails due to secure vault proxy error
Workflow execution fails at Telegram “Get a file” node with a secure vault proxy error (403), unable to fetch bot token from credential vault.
Mathesh Natarajan 7 days ago
🐛 Bug Reports
Completed
Telegram Get File node fails due to secure vault proxy error
Workflow execution fails at Telegram “Get a file” node with a secure vault proxy error (403), unable to fetch bot token from credential vault.
Mathesh Natarajan 7 days ago
🐛 Bug Reports
Completed
Gemini HTTP request fails despite authentication configured
Gemini API request fails with 404 error even though authentication is properly configured in the node, indicating auth or endpoint handling issue. n8n : indie : File :
Mathesh Natarajan 7 days ago
🐛 Bug Reports
Completed
Gemini HTTP request fails despite authentication configured
Gemini API request fails with 404 error even though authentication is properly configured in the node, indicating auth or endpoint handling issue. n8n : indie : File :
Mathesh Natarajan 7 days ago
🐛 Bug Reports
Completed
Gemini model node not accessible or supported
Certain model nodes (e.g., “Message a model”) are not accessible or supported, limiting functionality and preventing usage in workflows. Eg :
Mathesh Natarajan 7 days ago
🐛 Bug Reports
Completed
Gemini model node not accessible or supported
Certain model nodes (e.g., “Message a model”) are not accessible or supported, limiting functionality and preventing usage in workflows. Eg :
Mathesh Natarajan 7 days ago
🐛 Bug Reports
Completed
Wiring animation needs improvement for better flow visibility
Current wiring animation is unclear and not smooth, making it difficult to visually track connections and execution flow between nodes.
Mathesh Natarajan 7 days ago
🐛 Bug Reports
Completed
Wiring animation needs improvement for better flow visibility
Current wiring animation is unclear and not smooth, making it difficult to visually track connections and execution flow between nodes.
Mathesh Natarajan 7 days ago
🐛 Bug Reports
Completed
Incorrect routing to Stop and Error node instead of empty path
n8n : Indie : File : JSON : [ { "event_id": "EV-001", "user_email": "vip_client@tesla.com", "priority_level": 9, "event_type": "high_value_action" }, { "event_id": "EV-002", "user_email": "standard_user@gmail.com", "priority_level": 2, "event_type": "page_view" }, { "event_id": "EV-003", "user_email": "", "priority_level": 0, "event_type": "anonymous_ping" } ]
Mathesh Natarajan 7 days ago
🐛 Bug Reports
Completed
Incorrect routing to Stop and Error node instead of empty path
n8n : Indie : File : JSON : [ { "event_id": "EV-001", "user_email": "vip_client@tesla.com", "priority_level": 9, "event_type": "high_value_action" }, { "event_id": "EV-002", "user_email": "standard_user@gmail.com", "priority_level": 2, "event_type": "page_view" }, { "event_id": "EV-003", "user_email": "", "priority_level": 0, "event_type": "anonymous_ping" } ]
Mathesh Natarajan 7 days ago
🐛 Bug Reports
Completed
Random logout from indie.money
Users are being logged out unexpectedly without any action, disrupting workflow and session continuity.
Mathesh Natarajan 8 days ago
🐛 Bug Reports
Completed
Random logout from indie.money
Users are being logged out unexpectedly without any action, disrupting workflow and session continuity.
Mathesh Natarajan 8 days ago
🐛 Bug Reports
Completed
Automatic retries triggered without enabling retry on failure
Workflow engine retries execution automatically even when “Retry upon failure” is not enabled in the node, causing repeated failed runs. File :
Mathesh Natarajan 8 days ago
🐛 Bug Reports
Completed
Automatic retries triggered without enabling retry on failure
Workflow engine retries execution automatically even when “Retry upon failure” is not enabled in the node, causing repeated failed runs. File :
Mathesh Natarajan 8 days ago
🐛 Bug Reports
Completed
Telegram Get File node fails with invalid file_id error
Workflow execution fails at Telegram “Get a file” node due to invalid file_id, preventing file retrieval and subsequent processing File :
Mathesh Natarajan 8 days ago
🐛 Bug Reports
Completed
Telegram Get File node fails with invalid file_id error
Workflow execution fails at Telegram “Get a file” node due to invalid file_id, preventing file retrieval and subsequent processing File :
Mathesh Natarajan 8 days ago
🐛 Bug Reports
Completed
Basic LLM Chain fails due to unsupported Google Gemini Chat Model
Run ID: 7b54e484-ba71-4909-8321-03cccc34b7ca Workflow execution fails at Basic LLM Chain because Google Gemini Chat Model is not supported, causing sub-node error. File : Payload : { "customer_name": "John Doe", "feedback": "The product is amazing, but the delivery took 10 days which was frustrating." }
Mathesh Natarajan 8 days ago
🐛 Bug Reports
Completed
Basic LLM Chain fails due to unsupported Google Gemini Chat Model
Run ID: 7b54e484-ba71-4909-8321-03cccc34b7ca Workflow execution fails at Basic LLM Chain because Google Gemini Chat Model is not supported, causing sub-node error. File : Payload : { "customer_name": "John Doe", "feedback": "The product is amazing, but the delivery took 10 days which was frustrating." }
Mathesh Natarajan 8 days ago
🐛 Bug Reports
Completed
Missing or inconsistent animation in workflow execution
Workflow nodes (e.g., Loop Over Items, GraphQL) do not show proper execution animation, making it hard to track flow and execution state visually.
Mathesh Natarajan 8 days ago
🐛 Bug Reports
Completed
Missing or inconsistent animation in workflow execution
Workflow nodes (e.g., Loop Over Items, GraphQL) do not show proper execution animation, making it hard to track flow and execution state visually.
Mathesh Natarajan 8 days ago
🐛 Bug Reports
Completed
Workflow shows different behavior compared to n8n execution
Workflow execution results differ from expected behavior. Run ID : 6e70c1a3-86a2-4117-a42c-7da6618b9069 n8n : Payload : [ { "event_id": "EV-001", "user_email": "vip_client@tesla.com", "priority_level": 9, "event_type": "high_value_action" }, { "event_id": "EV-002", "user_email": "standard_user@gmail.com", "priority_level": 2, "event_type": "page_view" }, { "event_id": "EV-003", "user_email": "", "priority_level": 0, "event_type": "anonymous_ping" } ] File :
Mathesh Natarajan 8 days ago
🐛 Bug Reports
Completed
Workflow shows different behavior compared to n8n execution
Workflow execution results differ from expected behavior. Run ID : 6e70c1a3-86a2-4117-a42c-7da6618b9069 n8n : Payload : [ { "event_id": "EV-001", "user_email": "vip_client@tesla.com", "priority_level": 9, "event_type": "high_value_action" }, { "event_id": "EV-002", "user_email": "standard_user@gmail.com", "priority_level": 2, "event_type": "page_view" }, { "event_id": "EV-003", "user_email": "", "priority_level": 0, "event_type": "anonymous_ping" } ] File :
Mathesh Natarajan 8 days ago
🐛 Bug Reports
Completed
ClickUp Create Time Entry node fails with internal server error
Workflow execution fails at “Create a time entry” node with an internal server error, preventing successful time entry creation. Run ID: 0fbefe17-7798-4d92-ae0c-2a1e7b576e7c File :
Mathesh Natarajan 8 days ago
🐛 Bug Reports
Completed
ClickUp Create Time Entry node fails with internal server error
Workflow execution fails at “Create a time entry” node with an internal server error, preventing successful time entry creation. Run ID: 0fbefe17-7798-4d92-ae0c-2a1e7b576e7c File :
Mathesh Natarajan 8 days ago
🐛 Bug Reports