Data table description update: why a cached version is used by a flow?

1

Hello All,
It's required to update data table description periodically.
After every update from either UI or API (PUT request) flow displays the message:
"Item is different from the latest version. Flow is referencing a cached version of the item."

Questions:

  1. Why flows affected by the description update only?

  2. Does it mean that all flows should be re-published to access the data table?

  3. What is the recommended method to update data table description without the impact on flows?

2

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.