I think it should also trigger the code that says something has (potentially) changed and so cause a context flush at the next timeout. I doubt if that logic checks whether anything has actually changed, though I have not checked the code.
Colin
17
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| A guide to understanding 'Persistent Context' | 90 | 45615 | 31 August 2022 | |
| Node-red won't start | 64 | 3635 | 23 November 2020 | |
| Context store 'localfilesystem' not saved to file system | 19 | 670 | 23 February 2023 | |
| Losing global context variable | 10 | 788 | 21 May 2022 | |
| Generate retain variables using global.set/get | 11 | 990 | 15 December 2019 |