A parameterized data page is of node scope and reload every hour. An activity has 10 steps with each step's step page is the parameterized data page with same parameters. In each step, the system will check if the data page is fresh and reloaded if needed (as shown in Tracer). Though it is rare but possible that during processing this activity, the data page is expired in the middle. As such, the step 1 and step 10's data page content will be different.
What is the recommended design pattern if I need to maintain consistent data page content within the different steps of the activity? Is this something I sure even worry about?
If your design insists to keep this as a node-level data page rather than requestor scope, I think maybe there is an extremely rare possibility of new data page getting loaded in activity steps. Can you consider copying the parametrized data page to a temporary page at step1 that can be used as a step page to maintain consistency and later remove it after activity execution?