Forum Discussion

nxadmin's avatar
nxadmin
New Member
6 months ago

Fabric known issue ID 1719

Hello,

I am referring to Fabric known issue ID 1719: we have implementend activator alerts sending emails with context properties as parameters; we are using and do require the 'when it has been true for' condition in these alert rules. We want to move our solution to production, but unfortunately this is not possible with faulty emails where parameters are not rendering. Does anyone know when a fix for this issue can be expected? 

Tnx in advance and best, flo.

Activator

4 Replies

    • nxadmin's avatar
      nxadmin
      New Member
      6 months ago

      thank you! I know this site, it's actually where I came from.. but unfortunately it doesn't say anything about when a fix can be expected or what the progress is..

       

      • v-kpoloju-msft's avatar
        v-kpoloju-msft
        Icon for Community Support rankCommunity Support
        6 months ago

        Hi nxadmin, 

        Thank you for the clarification.

        You are right, the Known Issues page does not always include an expected timeline for a fix. Updates are usually added once the product team makes progress or releases a resolution.

        For now, the best option is to keep an eye on the Known Issues page for any updates. If this issue is significantly impacting your work, you may also consider opening a Microsoft support ticket so the support team can investigate your specific scenario.

        Please let us know if you have any additional details to share.

        Thank you.

  • Prince0011's avatar
    Prince0011
    Icon for Solution Sage rankSolution Sage
    2 months ago

    Hi Flo,

    Since this is already listed as Known Issue ID 1719, it's generally an indication that the Microsoft Fabric product team has acknowledged the problem and is working on a fix.

    Unfortunately, Microsoft doesn't typically publish an ETA for individual known issues unless it's announced in the Fabric release notes or the issue is updated on the Known Issues page. Until then, there isn't usually a way for the community to determine when the fix will be deployed.

    A few suggestions:

    • Keep an eye on the Fabric Known Issues page and the monthly Fabric updates for any status changes.

    • If this issue is blocking your production rollout, I'd recommend opening a Microsoft Support ticket. Support may be able to provide additional information on the issue's status or suggest a temporary workaround based on your scenario.

    • If possible, consider whether the alert can be redesigned temporarily without relying on the "when it has been true for" condition until the fix is available.

    If anyone from the Microsoft product team can share whether there is an expected timeline or a recommended workaround for Known Issue 1719, it would be greatly appreciated by those planning production deployments.

    If you found this reply helpful, please consider giving it a Kudos. If it answers your question, marking it as the Accepted Solution will help others tracking the same known issue.