<?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 Feature Request: Detailed I/O Debug Information for Conditions and Loops in Workato Pros Discussion Board</title>
    <link>https://systematic.workato.com/t5/workato-pros-discussion-board/feature-request-detailed-i-o-debug-information-for-conditions/m-p/11172#M4365</link>
    <description>&lt;P&gt;Dear Workato Team,&lt;BR /&gt;Thank you for continuously improving the platform and for the excellent support your team provides. I'd like to propose two debugging enhancements that would reduce overall troubleshooting time (at least for me &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; ).&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;1. Visible Input Data for Conditions&lt;BR /&gt;Currently, conditions only show the outcome (e.g., {condition: false}), but not the actual values being evaluated. This makes debugging difficult, especially within loops where some items match and others don't.&lt;BR /&gt;I propose: Display the evaluated inputs alongside the result:&lt;BR /&gt;json{&lt;BR /&gt;"value": "example_data",&lt;BR /&gt;"condition": "contains",&lt;BR /&gt;"match_against": "search_term"&lt;BR /&gt;}&lt;/P&gt;&lt;P&gt;2. Loop Iteration History&lt;BR /&gt;After job completion, loops only display the final iteration's state, making it hard to identify which specific iteration failed or behaved unexpectedly.&lt;BR /&gt;I propose to add an optional "debug mode" toggle for loop steps that captures input/output data for each iteration:&lt;BR /&gt;json{&lt;BR /&gt;"iteration_1": {"counter": 1},&lt;BR /&gt;"iteration_2": {"counter": 2},&lt;BR /&gt;"iteration_13": {"counter": 3}&lt;BR /&gt;}&lt;BR /&gt;I understand this could be resource-intensive for large loops, which is why making it an opt-in toggle would be reasonable.&lt;BR /&gt;These features would eliminate the need for workaround debug steps and make recipe troubleshooting much more efficient.&lt;BR /&gt;Best regards&lt;BR /&gt;Mike&lt;/P&gt;</description>
    <pubDate>Wed, 05 Nov 2025 19:45:09 GMT</pubDate>
    <dc:creator>mikefdy</dc:creator>
    <dc:date>2025-11-05T19:45:09Z</dc:date>
    <item>
      <title>Feature Request: Detailed I/O Debug Information for Conditions and Loops</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/feature-request-detailed-i-o-debug-information-for-conditions/m-p/11172#M4365</link>
      <description>&lt;P&gt;Dear Workato Team,&lt;BR /&gt;Thank you for continuously improving the platform and for the excellent support your team provides. I'd like to propose two debugging enhancements that would reduce overall troubleshooting time (at least for me &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; ).&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;1. Visible Input Data for Conditions&lt;BR /&gt;Currently, conditions only show the outcome (e.g., {condition: false}), but not the actual values being evaluated. This makes debugging difficult, especially within loops where some items match and others don't.&lt;BR /&gt;I propose: Display the evaluated inputs alongside the result:&lt;BR /&gt;json{&lt;BR /&gt;"value": "example_data",&lt;BR /&gt;"condition": "contains",&lt;BR /&gt;"match_against": "search_term"&lt;BR /&gt;}&lt;/P&gt;&lt;P&gt;2. Loop Iteration History&lt;BR /&gt;After job completion, loops only display the final iteration's state, making it hard to identify which specific iteration failed or behaved unexpectedly.&lt;BR /&gt;I propose to add an optional "debug mode" toggle for loop steps that captures input/output data for each iteration:&lt;BR /&gt;json{&lt;BR /&gt;"iteration_1": {"counter": 1},&lt;BR /&gt;"iteration_2": {"counter": 2},&lt;BR /&gt;"iteration_13": {"counter": 3}&lt;BR /&gt;}&lt;BR /&gt;I understand this could be resource-intensive for large loops, which is why making it an opt-in toggle would be reasonable.&lt;BR /&gt;These features would eliminate the need for workaround debug steps and make recipe troubleshooting much more efficient.&lt;BR /&gt;Best regards&lt;BR /&gt;Mike&lt;/P&gt;</description>
      <pubDate>Wed, 05 Nov 2025 19:45:09 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/feature-request-detailed-i-o-debug-information-for-conditions/m-p/11172#M4365</guid>
      <dc:creator>mikefdy</dc:creator>
      <dc:date>2025-11-05T19:45:09Z</dc:date>
    </item>
    <item>
      <title>Re: Feature Request: Detailed I/O Debug Information for Conditions and Loops</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/feature-request-detailed-i-o-debug-information-for-conditions/m-p/11174#M4366</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://systematic.workato.com/t5/user/viewprofilepage/user-id/12457"&gt;@mikefdy&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;Here’s the link where you can submit your ideas so the &lt;STRONG&gt;Workato Development Team&lt;/STRONG&gt; can review them and take them into consideration.&lt;BR /&gt;Link:&lt;BR /&gt;&lt;A href="https://ideas.workato.com/app/#/user/dashboard?currentProductId=caf1efdf-1d7e-4b7b-aeb9-28e4b0f4b25c&amp;amp;cpid=931134c4-fa0c-41ba-815c-c31e90cf9eaa" target="_blank"&gt;Visitor dashboard | Feedback&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;please let me know if you need further help.&lt;BR /&gt;&lt;BR /&gt;Thanks and Regards,&lt;BR /&gt;Shivakumara K A&lt;/P&gt;</description>
      <pubDate>Thu, 06 Nov 2025 09:29:16 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/feature-request-detailed-i-o-debug-information-for-conditions/m-p/11174#M4366</guid>
      <dc:creator>shivakumara</dc:creator>
      <dc:date>2025-11-06T09:29:16Z</dc:date>
    </item>
  </channel>
</rss>

