​@PotatoJedi Could you send a screen shot so I can validate this? 

Also, are you using Community Edition or your company’s control room? If you are using your company’s control room, is it cloud-based or on-premises?

​@PotatoJedi have you been able to resolve the issue?

Hello ​@Aaron.Gleason ​@Shreya.Kumar , apologies for the late update on my part. Thanks for checking in on my issue.  

Update regarding the issue and answer to some of the queries Aaron posted previously: 

- The issue was observed while using our company’s cloud based control room (not on-prem)
- We tried various things to try and resolve the issue, and I’m not exactly sure which of these approach actually fixed the issue, so I’ll just be listing down the steps we took here for future reference: 

• Our control room Admin removed and re-added the recommended roles for DA users 
• Afterwards we deleted the affected learning instance and created a new one
• The new learning instance was then published to public / checked-in 
• After publishing to public, I believe it was also added by our admin to a document automation group/team. 

I have yet to encounter the issue after these steps were done. I’m not sure if one or all of these together solved the issue, but it seems to have worked for us. 

Additional note: We also contacted AA support in relation to a different Document automation issue. The conclusion AA support team arrived to regarding that issue was that it was most likely caused by our use of the “Test Mode” in DA, apparently there are known bugs affecting Test Mode which should be fixed by the next patch in a few months time. 

Now, I can’t exactly recall whether I encountered the aforementioned Cluster issue while using Test mode, and unfortunately, I can’t check as we’ve deleted the affected learning instance. But I thought to point it out for anybody who might encounter the same issue while using Test Mode. 

Stay safe and healthy. And thanks again :)