Incorrect scene7Filestatus post publishing the asset. | Community
Skip to main content
Level 3
August 31, 2020
Solved

Incorrect scene7Filestatus post publishing the asset.

  • August 31, 2020
  • 1 reply
  • 4978 views

Hi Team,

Please find the issue explanation as below.

 

scene7FileStatus - On our production environment, Few assets falls under the incorrect scene7FileStatus everyday.

We are trying to find root cause but unable the re-produce issue on lower environment.

 

Steps :

1] Upload the asset.

2] Enrich the metadata

3] Publish the asset to publish environment.

4] Asset also upload to scene7 bucket as we have configured it , so upon activation it's uploaded to it.

5] Issue : Scene7FileStatus should be convert to PublishComplete from PublishIncomplete. 

 

But for few assets it's not converting to PublishComplete, on republishing the asset it's went to right status, but we are trying to find cause for the issue while it's publishing for first time, it's not fall in right status for few asset everyday.

 

Please advise. We are using AEM 6.5.2.

 

Thanks

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by vikasbharti

Hi,

There could be many reasons why an asset gets stuck in PublishIncomplete. I suggest opening a support ticket with us along with complete error logs and if possible adding debugger logs[0] capturing specific calls to the dm cloud for further investigation. Also, I would recommend upgrading the instance to the latest service pack as we've fixed quite a number of bugs/issues related to the processing of assets in SP4 and above.

[0] 

• com.day.cq.dam.scene7 = communication between AEM and Scene7.

• com.day.cq.dam.scene7.impl.Scene7APIClientImpl = keep track of uploads
• com.adobe.cq.dam.ips = keep track of uploads

1 reply

vikasbhartiAdobe EmployeeAccepted solution
Adobe Employee
August 31, 2020

Hi,

There could be many reasons why an asset gets stuck in PublishIncomplete. I suggest opening a support ticket with us along with complete error logs and if possible adding debugger logs[0] capturing specific calls to the dm cloud for further investigation. Also, I would recommend upgrading the instance to the latest service pack as we've fixed quite a number of bugs/issues related to the processing of assets in SP4 and above.

[0] 

• com.day.cq.dam.scene7 = communication between AEM and Scene7.

• com.day.cq.dam.scene7.impl.Scene7APIClientImpl = keep track of uploads
• com.adobe.cq.dam.ips = keep track of uploads
Level 3
August 31, 2020

Thank you for your swift response vikas. sure, We will propose to upgrade the instance to latest service pack.

 

Before that you mentioned no of reason asset stuck in incorrect state. May i know few reasons? 

 

Also you mentioned fix processes related fix in latest service pack. Is there anyone change around this?