"The flow that you use to repopulate the cache after adding a new row to the DB table to be cached must literally be the same flow that is used for the initial populating of the cache - not even another flow in the same EG."
Correct. If that was not the case then you would not need to separate out the cache into its own flow. The reason is that a SHARED variable is scoped to a single flow so if two different flows have the same named SHARED variable then you actually have two different variables.
But as you found, putting a second input node into the callable flow (Flow1) allows you to update the cache when required. An alternative that works well when you need to update the cache more frequently is to have a "Timeout Notification" node in your Flow1 that will periodically fire to call a node to update the cache on a regular interval.
Hope that helps... _________________ MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum