<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Ensuring Workflow Reliability: Challenges, Best Practices and workflow self-monitoring in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Ensuring-Workflow-Reliability-Challenges-Best-Practices-and/m-p/293259#M38484</link>
    <description>&lt;P&gt;Would the built-in notifications solve your question? &lt;A href="https://docs.dynatrace.com/docs/shortlink/workflows-notifications" target="_blank"&gt;https://docs.dynatrace.com/docs/shortlink/workflows-notifications&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;They are off by default. Also if the part of a workflow fails, you can handle it within the workflow and provide a different notification or log this. For example querying external system fails.&lt;/P&gt;</description>
    <pubDate>Mon, 19 Jan 2026 07:18:51 GMT</pubDate>
    <dc:creator>Julius_Loman</dc:creator>
    <dc:date>2026-01-19T07:18:51Z</dc:date>
    <item>
      <title>Ensuring Workflow Reliability: Challenges, Best Practices and workflow self-monitoring</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Ensuring-Workflow-Reliability-Challenges-Best-Practices-and/m-p/293257#M38483</link>
      <description>&lt;P&gt;Hi Folks,&lt;/P&gt;&lt;P&gt;Currently, many people are transitioning from alerting profiles and problem notifications to workflows.&lt;/P&gt;&lt;P&gt;This shift offers significant advantages, particularly in manipulating problem descriptions.&lt;/P&gt;&lt;P&gt;However, this transition also introduces challenges, such as the potential for workflow failures.&lt;/P&gt;&lt;P&gt;We've observed instances where workflows fail, resulting in missed problems.&lt;/P&gt;&lt;P&gt;From my experience, problem notifications have never failed, whereas workflows can fail for various reasons.&lt;/P&gt;&lt;P&gt;My question is: Given the importance of workflows, how can we ensure their reliability? What are the best and simplest methods to monitor workflows or detect failed executions with alerts?&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;AK&lt;/P&gt;</description>
      <pubDate>Sun, 18 Jan 2026 22:42:51 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Ensuring-Workflow-Reliability-Challenges-Best-Practices-and/m-p/293257#M38483</guid>
      <dc:creator>AK</dc:creator>
      <dc:date>2026-01-18T22:42:51Z</dc:date>
    </item>
    <item>
      <title>Re: Ensuring Workflow Reliability: Challenges, Best Practices and workflow self-monitoring</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Ensuring-Workflow-Reliability-Challenges-Best-Practices-and/m-p/293259#M38484</link>
      <description>&lt;P&gt;Would the built-in notifications solve your question? &lt;A href="https://docs.dynatrace.com/docs/shortlink/workflows-notifications" target="_blank"&gt;https://docs.dynatrace.com/docs/shortlink/workflows-notifications&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;They are off by default. Also if the part of a workflow fails, you can handle it within the workflow and provide a different notification or log this. For example querying external system fails.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jan 2026 07:18:51 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Ensuring-Workflow-Reliability-Challenges-Best-Practices-and/m-p/293259#M38484</guid>
      <dc:creator>Julius_Loman</dc:creator>
      <dc:date>2026-01-19T07:18:51Z</dc:date>
    </item>
  </channel>
</rss>

