<?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: Error when sending shortcut : Could not identify process owning the current foreground window in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Error-when-sending-shortcut-Could-not-identify-process-owning/m-p/111928#M50213</link>
    <description>&lt;P&gt;I profit to add that these errors were triggered after an update of the application where the process is supposed to send the shortcut, with this update the application changed from 32 bit to 64 bit.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 27 Jun 2024 13:53:06 GMT</pubDate>
    <dc:creator>PMSB7</dc:creator>
    <dc:date>2024-06-27T13:53:06Z</dc:date>
    <item>
      <title>Error when sending shortcut : Could not identify process owning the current foreground window</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Error-when-sending-shortcut-Could-not-identify-process-owning/m-p/111919#M50211</link>
      <description>&lt;P&gt;Hello Guys.&lt;/P&gt;&lt;P&gt;Every time I execute a global send key events action within a process through the control room by schedule I have the following error: "&lt;SPAN&gt;&lt;SPAN class=""&gt;An error has occurred while sending {{ALT}PNL} short keys in order to open ... || ERROR: Failed to perform step 1 in Navigate Stage ... - Could not identify process owning the current foreground window".&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;The strangest is that if the process is executed manually everything works fine.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;Do you have clue of how to tackle this issue?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;Thank you&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jun 2024 10:57:57 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Error-when-sending-shortcut-Could-not-identify-process-owning/m-p/111919#M50211</guid>
      <dc:creator>PMSB7</dc:creator>
      <dc:date>2024-06-27T10:57:57Z</dc:date>
    </item>
    <item>
      <title>Re: Error when sending shortcut : Could not identify process owning the current foreground window</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Error-when-sending-shortcut-Could-not-identify-process-owning/m-p/111928#M50213</link>
      <description>&lt;P&gt;I profit to add that these errors were triggered after an update of the application where the process is supposed to send the shortcut, with this update the application changed from 32 bit to 64 bit.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jun 2024 13:53:06 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Error-when-sending-shortcut-Could-not-identify-process-owning/m-p/111928#M50213</guid>
      <dc:creator>PMSB7</dc:creator>
      <dc:date>2024-06-27T13:53:06Z</dc:date>
    </item>
  </channel>
</rss>

