Grasshopper 3.24.32.3 Release Notes
Defect Fixes
Bug Fix: Lasso Plugin Failing to Execute Due to Undefined Variable Error
Overview
During routine production monitoring, support teams identified that the Lasso plugin was failing to execute on every invocation.
This indicated that one of the internal variables used within the plugin’s execution pipeline was not properly initialized or referenced at runtime.
Key Fixes
- Corrected Undefined Variable Reference
Resolved the root cause by defining and properly initializing the pipelineCountStage variable before execution, preventing the ReferenceError during plugin invocation.
- Restored Plugin Execution Flow
The Lasso plugin now runs end-to-end as expected on each invocation, without premature termination.
- Improved Error Handling & Stability
Additional guard checks were introduced to ensure missing pipeline components cannot break execution flow in future iterations.
- Log Clean-Up
Error noise has been eliminated from the logs, allowing accurate monitoring of plugin success/failure events.
Bug Fix: Unable to Update Orders to Consolidated Due to Missing Address Reference
Overview
Client reported that certain orders could not be updated to Consolidated status when items were received at the hub.
During the receipt workflow, the system presented an error preventing the status transition.
Grasshopper production logs confirmed the issue, and internal attempts to reproduce resulted in the same failure. This indicated that the UI attempted to access an address property that was not available in the expected object structure, causing the workflow to halt.
Key Fixes
- Corrected Address Reference Handling
Fixed a UI logic path where the Consolidation flow attempted to read address data from an undefined or partially loaded order object.
- Ensured Proper Data Initialization
Added defensive loading logic to guarantee all required address fields are present before the Consolidate action is triggered.
- Stabilized Consolidation Workflow
The transition to Consolidated now completes successfully for all orders, including those without complete address metadata at the moment of scanning or receiving.
- Improved Error Messaging & Logging
Updated internal validation to prevent undefined reference errors and enhance troubleshooting visibility.
Bug Fix: Disabled Consolidation Report Scheduler During Report Decommissioning
Overview
As part of the planned decommissioning of the Consolidation Report, the associated automated scheduler continued to run in the background. To ensure a clean retirement of the feature and avoid confusion for operations teams, the scheduler has now been fully disabled.
Key Fixes
- Scheduler Deactivation
The automated job responsible for generating the Consolidation Report has been fully disabled to prevent further runs.
- Alignment With Report Removal Process
Ensured that all backend triggers referencing the old report are inactive, matching the decommissioning timeline.
- Prevention of Future Invocations
Added a safeguard preventing any accidental reactivation of the scheduler until the report is permanently removed.