We have several Events configured in the old Creator Studio (old) that send a Teams notification as soon as the Power Automate flow receives a payload. Two additional events are also tied to this flow. When users receive the notification, they are presented with Approve and Deny buttons, which trigger corresponding Power Automate flows. These flows interact with the Planview API to patch the required task numbers.
However, an issue has been observed:
If a request is created (for example, on 30th January) and the user attempts to approve or deny it after 3–4 days, the event‑based path no longer triggers, causing the downstream process to stop.
We would like to know whether there is any platform limitation or time‑bound restriction where a static Teams message (triggered by an event) can only remain actionable for a certain duration, after which the Approve/Deny actions cannot be executed. If such a limitation exists, please confirm. Additionally, if there are any recommended workarounds or best practices, kindly advise, as end users are currently facing issues.