<?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: AEM 6.4 Assets | DAM Update Workflow fails but shows as RUNNING in Adobe Experience Manager Discussions</title>
    <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-4-assets-dam-update-workflow-fails-but-shows-as-running/m-p/426396#M30254</link>
    <description>&lt;P&gt;&lt;LI-USER uid="10527152"&gt;&lt;/LI-USER&gt;&amp;nbsp;I think you might be storing the assets in &lt;SPAN&gt;&amp;nbsp;S7 instead of DAM it seems this issue is related to the connectivity with S7 . You need to check the corresponding API properly. If you are using any java service in the S7 upload step then try to debug it through&amp;nbsp;debugger to check code step by step your code.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thank You.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 06 Oct 2021 11:26:31 GMT</pubDate>
    <dc:creator>kchaurasiya</dc:creator>
    <dc:date>2021-10-06T11:26:31Z</dc:date>
    <item>
      <title>AEM 6.4 Assets | DAM Update Workflow fails but shows as RUNNING</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-4-assets-dam-update-workflow-fails-but-shows-as-running/m-p/353998#M24937</link>
      <description>&lt;P&gt;As per default AEM behaviour, when uploading/updating an Asset, DAM Update Asset workflow is triggered - in our setup this includes a S7 upload step.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Problem&lt;/STRONG&gt;:&lt;/P&gt;&lt;P&gt;In some cases we get an exception such as&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;repository conflict exception for an asset,&amp;nbsp; or&lt;/LI&gt;&lt;LI&gt;S7 timeout exception as shown below&lt;/LI&gt;&lt;/UL&gt;&lt;LI-CODE lang="markup"&gt;com.adobe.granite.workflow.WorkflowException: --Dynamic Media asset process failed. Please contact your system administrator.-- /content/dam/myasset.jpg
	at com.day.cq.workflow.compatibility.CQWorkflowExtProcessProxy.handleResult(CQWorkflowExtProcessProxy.java:99)
	at com.adobe.granite.workflow.core.util.WEPProxyHolder.handleResult(WEPProxyHolder.java:50)
	at com.adobe.granite.workflow.core.job.ExternalProcessPollingHandler.process(ExternalProcessPollingHandler.java:129)
	at org.apache.sling.event.impl.jobs.JobConsumerManager$JobConsumerWrapper.process(JobConsumerManager.java:502)
	at org.apache.sling.event.impl.jobs.queues.JobQueueImpl.startJob(JobQueueImpl.java:293)
	at org.apache.sling.event.impl.jobs.queues.JobQueueImpl.access$100(JobQueueImpl.java:60)
	at org.apache.sling.event.impl.jobs.queues.JobQueueImpl$1.run(JobQueueImpl.java:229)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: com.day.cq.dam.scene7.api.model.IpsApiException: org.apache.http.NoHttpResponseException: s7sps3apissl.scene7.com:443 failed to respond
	at com.day.cq.dam.scene7.impl.Scene7APIClientImpl.makeRequest(Scene7APIClientImpl.java:356)
	at com.day.cq.dam.scene7.impl.Scene7APIClientImpl.searchAssets(Scene7APIClientImpl.java:1178)
	at com.day.cq.dam.scene7.impl.Scene7ServiceImpl.searchAssetsByFilename(Scene7ServiceImpl.java:489)
	at com.day.cq.dam.scene7.impl.process.Scene7UploadProcess.getAssetHandle(Scene7UploadProcess.java:871)
	at com.day.cq.dam.scene7.impl.process.Scene7UploadProcess.handleSingleAssetUploadResult(Scene7UploadProcess.java:1078)
	at com.day.cq.dam.scene7.impl.process.Scene7UploadProcess.handleResult(Scene7UploadProcess.java:1020)
	at com.day.cq.workflow.compatibility.CQWorkflowExtProcessProxy.handleResult(CQWorkflowExtProcessProxy.java:97)
	... 9 more
Caused by: org.apache.http.NoHttpResponseException: s7sps3apissl.scene7.com:443 failed to respond
	at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:141)
	at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:56)
	at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:259)
	at org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:163)
	at org.apache.http.impl.conn.CPoolProxy.receiveResponseHeader(CPoolProxy.java:165)
	at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:273)
	at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
	at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:272)
	at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185)
	at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
	at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:111)
	at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:108)
	at com.day.cq.dam.scene7.impl.Scene7APIClientImpl.getResponse(Scene7APIClientImpl.java:424)
	at com.day.cq.dam.scene7.impl.Scene7APIClientImpl.makeRequest(Scene7APIClientImpl.java:342)
	... 15 more&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In such cases, the failure shows as an inbox notification (thus allowing us to manually identify such failures and retry the step).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, the workflow instance itself shows as "Running" instead of "Failed", which&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;imho is a bit counter-intuitive&lt;/LI&gt;&lt;LI&gt;we cannot effectively get such failed workflow instances via &lt;A href="https://docs.adobe.com/content/help/en/experience-manager-64/developing/extending-aem/extending-workflows/workflows-program-interaction.html#managing-workflow-instances" target="_self"&gt;AEM Workflow REST API&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;The above can occur for a failure at any step, the repo conflict is the most common issue we get however.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Question(s)&lt;/STRONG&gt;:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;is there a workaround for this, to allow the aforementioned API usage?&lt;/LI&gt;&lt;LI&gt;is there an effective (ideally OOTB) way to retry the failed step?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you in advance for your help.&lt;/P&gt;</description>
      <pubDate>Fri, 08 Oct 2021 17:01:17 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-4-assets-dam-update-workflow-fails-but-shows-as-running/m-p/353998#M24937</guid>
      <dc:creator>kimonp31365843</dc:creator>
      <dc:date>2021-10-08T17:01:17Z</dc:date>
    </item>
    <item>
      <title>Re: AEM 6.4 Assets | DAM Update Workflow fails but shows as RUNNING</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-4-assets-dam-update-workflow-fails-but-shows-as-running/m-p/426390#M30252</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;LI-USER uid="10527152"&gt;&lt;/LI-USER&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Did you get any solution to this problem?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thx.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Oct 2021 10:34:22 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-4-assets-dam-update-workflow-fails-but-shows-as-running/m-p/426390#M30252</guid>
      <dc:creator>Vinodthakur</dc:creator>
      <dc:date>2021-10-06T10:34:22Z</dc:date>
    </item>
    <item>
      <title>Re: AEM 6.4 Assets | DAM Update Workflow fails but shows as RUNNING</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-4-assets-dam-update-workflow-fails-but-shows-as-running/m-p/426391#M30253</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;LI-USER uid="17376316"&gt;&lt;/LI-USER&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Unfortunately no - eventually we just checked the WF instance node properties to get the failing status, so no direct indication of failure.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kind regards&lt;/P&gt;</description>
      <pubDate>Wed, 06 Oct 2021 10:37:48 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-4-assets-dam-update-workflow-fails-but-shows-as-running/m-p/426391#M30253</guid>
      <dc:creator>kimonp31365843</dc:creator>
      <dc:date>2021-10-06T10:37:48Z</dc:date>
    </item>
    <item>
      <title>Re: AEM 6.4 Assets | DAM Update Workflow fails but shows as RUNNING</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-4-assets-dam-update-workflow-fails-but-shows-as-running/m-p/426396#M30254</link>
      <description>&lt;P&gt;&lt;LI-USER uid="10527152"&gt;&lt;/LI-USER&gt;&amp;nbsp;I think you might be storing the assets in &lt;SPAN&gt;&amp;nbsp;S7 instead of DAM it seems this issue is related to the connectivity with S7 . You need to check the corresponding API properly. If you are using any java service in the S7 upload step then try to debug it through&amp;nbsp;debugger to check code step by step your code.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thank You.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Oct 2021 11:26:31 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-4-assets-dam-update-workflow-fails-but-shows-as-running/m-p/426396#M30254</guid>
      <dc:creator>kchaurasiya</dc:creator>
      <dc:date>2021-10-06T11:26:31Z</dc:date>
    </item>
  </channel>
</rss>

