I’ve encountered an issue specifically with the “Execute Workflow” node when reviewing past executions, and this behavior persists in n8n version 1.9.4 (running in queue mode) .
When I navigate to the execution history of a workflow and open a specific past run, if I then click on an “Execute Workflow” node (to see the details of the sub-workflow’s execution for that run), the output data section for nodes within that sub-workflow incorrectly displays the warning message: “Node parameters have changed. Test node again to refresh output.”
The warning would not be a such a big issue. This doesn’t break anything or stop the program from working, but it might make someone wonder if something went wrong.
You make a fair point that the program continues to function. However, for users analyzing past executions, an erroneous ‘parameters changed’ warning is misleading. Adding to this, the warning also hides the node’s specific execution data (start time, duration, etc.), diminishing the interface’s usability for review purposes. This feels like a bug that, while perhaps not critical, affects the polish, trustworthiness, and practical utility of reviewing historical data.
It’s important that such details continue to get attention, even as other exciting features are being developed
