<?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 chaining multiple workflows and detecting data updates in Alteryx Server Discussions</title>
    <link>https://community.alteryx.com/t5/Alteryx-Server-Discussions/chaining-multiple-workflows-and-detecting-data-updates/m-p/984634#M11429</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Hi Alteryx community,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I would like to know if there is a way / best practice to detect a.) the presence of a new file and b.) chain multiple Alteryx workflows one after the other based on the running of a previous workflows.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;My use case is the following: &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;IT run an automated DB extract roughly every 2h creating a csv file that is to be consumed. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The file is very large and delivery can fail / be delayed on IT side. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I would like to process the file asap when it gets delivered to maintain an up-to-date view of my data.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The first round of processing is very compute intensive and can take over 1h on the gallery server. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Therefore this step should only be processed if there has been an update to the DB extract file.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;After a successful run, further workflows should be triggered, processing that data in different ways.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Further data processing steps should be independent of each other (one failing should only impact downstream workflows but not prevent parallel workflows from running) &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Further workflows should be chained bottom-up so different teams can build solutions off the previous processing steps independently. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The initial up stream processing workflow should be agnostic of downstream processing so there is no need to touch the code of the original workflow (&lt;/SPAN&gt;&lt;SPAN&gt;The chaining functionality in Alteryx does not meet the requirement as it needs to chain the following workflows top down).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The current solution, is to write a log file when the initial file has been last processed. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Then check the DB output file when it was last modified &amp;amp; process if it was not processed before. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;This Alteryx check runs on the gallery every 10 mins &amp;amp; generates a lot of overhead &amp;amp; is absolutely not scalable to multiple processing steps without creating a lot of server load. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;So my questions are, is there a lightweight way to check if a file has been created/modified on a shared drive &amp;amp; trigger an workflow based on that. If so, that would solve both issues stated above (we would chain the downstream workflows based on output file of initial workflow).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;If there is no such way, is there the possibility to have a 'listener' on workflow A that signals when A has executed and workflows B,C and D get triggered automatically?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Open to any other ideas and suggestions &amp;amp; thanks in advance for your thoughts.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Cheers&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 17 Aug 2022 10:32:32 GMT</pubDate>
    <dc:creator>psyberbrain</dc:creator>
    <dc:date>2022-08-17T10:32:32Z</dc:date>
    <item>
      <title>chaining multiple workflows and detecting data updates</title>
      <link>https://community.alteryx.com/t5/Alteryx-Server-Discussions/chaining-multiple-workflows-and-detecting-data-updates/m-p/984634#M11429</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi Alteryx community,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I would like to know if there is a way / best practice to detect a.) the presence of a new file and b.) chain multiple Alteryx workflows one after the other based on the running of a previous workflows.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;My use case is the following: &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;IT run an automated DB extract roughly every 2h creating a csv file that is to be consumed. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The file is very large and delivery can fail / be delayed on IT side. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I would like to process the file asap when it gets delivered to maintain an up-to-date view of my data.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The first round of processing is very compute intensive and can take over 1h on the gallery server. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Therefore this step should only be processed if there has been an update to the DB extract file.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;After a successful run, further workflows should be triggered, processing that data in different ways.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Further data processing steps should be independent of each other (one failing should only impact downstream workflows but not prevent parallel workflows from running) &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Further workflows should be chained bottom-up so different teams can build solutions off the previous processing steps independently. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The initial up stream processing workflow should be agnostic of downstream processing so there is no need to touch the code of the original workflow (&lt;/SPAN&gt;&lt;SPAN&gt;The chaining functionality in Alteryx does not meet the requirement as it needs to chain the following workflows top down).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The current solution, is to write a log file when the initial file has been last processed. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Then check the DB output file when it was last modified &amp;amp; process if it was not processed before. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;This Alteryx check runs on the gallery every 10 mins &amp;amp; generates a lot of overhead &amp;amp; is absolutely not scalable to multiple processing steps without creating a lot of server load. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;So my questions are, is there a lightweight way to check if a file has been created/modified on a shared drive &amp;amp; trigger an workflow based on that. If so, that would solve both issues stated above (we would chain the downstream workflows based on output file of initial workflow).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;If there is no such way, is there the possibility to have a 'listener' on workflow A that signals when A has executed and workflows B,C and D get triggered automatically?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Open to any other ideas and suggestions &amp;amp; thanks in advance for your thoughts.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Cheers&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Aug 2022 10:32:32 GMT</pubDate>
      <guid>https://community.alteryx.com/t5/Alteryx-Server-Discussions/chaining-multiple-workflows-and-detecting-data-updates/m-p/984634#M11429</guid>
      <dc:creator>psyberbrain</dc:creator>
      <dc:date>2022-08-17T10:32:32Z</dc:date>
    </item>
    <item>
      <title>Re: chaining multiple workflows and detecting data updates</title>
      <link>https://community.alteryx.com/t5/Alteryx-Server-Discussions/chaining-multiple-workflows-and-detecting-data-updates/m-p/984882#M11430</link>
      <description>&lt;P&gt;what's your server/cloud/db combo? can you use something like cloud function/lambda after your file is written to trigger your Alteryx workflow via api?&lt;/P&gt;</description>
      <pubDate>Wed, 17 Aug 2022 16:46:43 GMT</pubDate>
      <guid>https://community.alteryx.com/t5/Alteryx-Server-Discussions/chaining-multiple-workflows-and-detecting-data-updates/m-p/984882#M11430</guid>
      <dc:creator>apathetichell</dc:creator>
      <dc:date>2022-08-17T16:46:43Z</dc:date>
    </item>
  </channel>
</rss>

