chore(release): staging to production - 2026.03.04 - #997
Merged
Conversation
Wraps all property access in optional chaining and try-catch blocks
to prevent TypeError when objects are undefined.
The 'filePath' error was likely from trying to log an object property
that didn't exist, causing the logging itself to throw errors.
Changes:
- Use optional chaining (?.) for all object property access in logs
- Wrap Object.keys() calls in try-catch
- Add fallback values ('NONE', 'UNKNOWN', 'N/A') for undefined properties
- Wrap entire logging blocks in try-catch where complex objects are logged
This ensures debug logging never crashes the application.
Fixes TypeError: Cannot read properties of undefined (reading 'filePath') The buildFlow function was accessing componentNodes[nodeName].filePath without checking if the node exists in the component pool first. This causes crashes when: - A node isn't properly registered - A node name doesn't match the pool keys - The component pool hasn't finished loading Added guards in 3 locations: 1. buildFlow main loop (line 592) 2. clearSessionMemory (line 832) 3. getSessionChatHistory (line 1843) Now logs an error and continues instead of crashing the entire flow.
…ging Debug/mcp comprehensive logging
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
maxtechera
temporarily deployed
to
staging - aai-unified2-flowise-moonstruck
March 4, 2026 15:30 — with 
Render
Inactive
Render
Inactive
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚀 Release: Staging to Production
Release Date: 2026-03-04
Changes in this release
This PR is automatically created/updated when commits are pushed to staging.
Merging this PR will trigger the release workflow to create a new GitHub release.