I have just published node-red-contrib-queue-gate version 1.5.5, which should resolve the issue in Case 1. Since the node has no way of knowing whether the context store selected by the user supports synchronous operations, I have used the form for asynchronous access everywhere. Please let me know if you run into any further issues. I would be very interested in knowing whether you get any changes or improvements by running with the cache disabled.
2 Likes
