<?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: Databricks Workflow duration issues in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/databricks-workflow-duration-issues/m-p/98706#M39810</link>
    <description>&lt;P&gt;This is already reported on a feature request to make sure we set a difference in between the queue time and the execution time in the job UI page, this can be tracked with id DB-I-8963&lt;/P&gt;</description>
    <pubDate>Wed, 13 Nov 2024 18:26:32 GMT</pubDate>
    <dc:creator>Walter_C</dc:creator>
    <dc:date>2024-11-13T18:26:32Z</dc:date>
    <item>
      <title>Databricks Workflow duration issues</title>
      <link>https://community.databricks.com/t5/data-engineering/databricks-workflow-duration-issues/m-p/98698#M39807</link>
      <description>&lt;P&gt;There is a discrepancy in the Databricks Workflow . Currently, the start and end times printed are when the workflow is triggered, not when the actual workflow execution begins. Ideally, it should log the task execution time. The issue is that the current implementation includes queuing time, which is not the intended behavior.&lt;/P&gt;&lt;P&gt;For example, if the threshold is set to 60 minutes, the expectation is that the task execution time should not exceed 60 minutes, but it is currently counting the time spent in the queue, which is not correct.&lt;/P&gt;&lt;P&gt;Any advise to fix ?&lt;/P&gt;</description>
      <pubDate>Wed, 13 Nov 2024 16:44:31 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricks-workflow-duration-issues/m-p/98698#M39807</guid>
      <dc:creator>ChsAIkrishna</dc:creator>
      <dc:date>2024-11-13T16:44:31Z</dc:date>
    </item>
    <item>
      <title>Re: Databricks Workflow duration issues</title>
      <link>https://community.databricks.com/t5/data-engineering/databricks-workflow-duration-issues/m-p/98706#M39810</link>
      <description>&lt;P&gt;This is already reported on a feature request to make sure we set a difference in between the queue time and the execution time in the job UI page, this can be tracked with id DB-I-8963&lt;/P&gt;</description>
      <pubDate>Wed, 13 Nov 2024 18:26:32 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricks-workflow-duration-issues/m-p/98706#M39810</guid>
      <dc:creator>Walter_C</dc:creator>
      <dc:date>2024-11-13T18:26:32Z</dc:date>
    </item>
    <item>
      <title>Re: Databricks Workflow duration issues</title>
      <link>https://community.databricks.com/t5/data-engineering/databricks-workflow-duration-issues/m-p/98783#M39839</link>
      <description>&lt;P&gt;Thank you for your reply and tracking ID&lt;/P&gt;</description>
      <pubDate>Thu, 14 Nov 2024 11:20:29 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricks-workflow-duration-issues/m-p/98783#M39839</guid>
      <dc:creator>ChsAIkrishna</dc:creator>
      <dc:date>2024-11-14T11:20:29Z</dc:date>
    </item>
  </channel>
</rss>

