Description
After upgrading NocoBase from version 2.0.8 to 2.1.18 and subsequently to 2.1.7-full (hosted on Railway), we can no longer view any Workflow Node Results in the execution history.
When clicking on the “View Node Result” button of any node (including newly executed workflows and historical executions from v2.0.8), the drawer/modal opens but gets stuck in an infinite loading spinner and never renders the data.
The workflow engine itself works perfectly in the background, and all backend data is processed successfully.
Network Request & Response Analysis
The backend functions properly. When checking the browser’s Network tab (F12) upon clicking the node, the API request successfully returns a 200 OK status with the complete data payload, but the UI fails to stop loading.
- Endpoint called:
/api/jobs:get?filterByTk=<JOB_ID> - HTTP Status: 200 OK
- JSON Response Sample (from a failing node):
Environment Context
- NocoBase Version: Upgraded from
2.0.8→2.1.8→ Currently on2.1.7-full. - Deployment Platform: Railway Hosting (PostgreSQL).
- Troubleshooting Done: Executed
yarn nocobase upgrade,yarn nocobase clean, and fully re-built the frontend application. Tested on multiple browsers via Incognito mode, but both old and new logs are stuck spinning.
It looks like the client-v2 logger component has a regression bug or an unhandled exception (possibly when parsing null fields or object mapping) inside the /api/jobs data visualizer. Please help investigate.
