Our team has built a Flow that we want to automate our WBR. We are using Topics that pull in data we also use for dashboards, so it is easy to check if the data is up to date.
Despite this our flow often reports data is missing for the latest week, and in some cases past weeks we have already reported on. It also often does not acknowledge the latest reporting week e.g. It still reports on wk13 as the latest when wk14 has completed and data shows elsewhere. We can run the Flow again and see it then include all of the data and complete the WBR, or in some cases pull in half the information. It feels very much like random luck if the report runs first time.
How do we improve Flows so we can rely on them? This is preventing us scaling across teams when we know our Flow steps work, just not every time.
I have seen a couple of other community users make similar observations. From your scenario, it sounds like you are interacting your data via a topic and a dashboard. Unfortunately, there is currently not much that can be done to try and fix this behavior.
Since flows are built upon prompts, you can try to mess around with that to see if the output changes. One thing you can also do is create a step in your flow that basically confirms the date before trying to pull all the associated information for that date. So hypothetically you create a step that confirms it is wk14 and that way it is like a sanity check to make sure the model is interpreting your prompts correctly. I have not tested that so I cannot promise that will actually work.
One other thing you can also do is submit a support ticket and the support team will be able to investigate into this issue. Please refer to this resource on how to submit a ticket (Case management - AWS Support).