Hi, this instance was given to us by Adobe after we requested support on our on-prem and Azure instance.  So we didn't do the install ourselves.  An Adobe employee did the install.

Hi,Augusto was assigned to another project and I am taking over this task. Also when Augusto said they, he meant the Adobe consultant he was working with at the time, setup this sandbox on Adobe cloud infrastructure.  I am not getting the error he is getting, but I am getting this popup on our custo...

This is what is showing on our error log, mostly SSL related.LevelDate / TimeMessage[ERROR]2019-09-2309:34:31Failed to validate URL http://www.adobe.com/go/learn_aemforms_install_65: javax.net.ssl.SSLException: Connection resetcom.day.cq.rewriter.linkchecker.impl.LinkCheckerTask[ERROR]2019-09-2308:3...

Yes, it is accessible and able to send email from the publish instance which is hosted on the same server with different port.Could it be that the e-mail is working but the Adaptive Forms workflow only works in edit mode?

They have been configured

Just to give more information about about our current setup we have an Azure instance for Author and Publish, in the Author /editor/html/content/formname.html works, but /content/formname.html does not work.  In Publish /content/formname.html does not work.  When I say work I mean the e-mail is sent...

We have an adaptive form that sends out an e-mail on submission.  It is part of a flow, the form works as intended when the page is in edit mode, i.e with the "editor.html" in the URL localhost:4502/editor.html/content/formname.html in the author instance.  But when we publish the form to localhost:...

Thank you for pointing us in the right direction.  We were able to get the publish agent working again and now the publishing works in Author. Although we did struggle with the adaptive forms not publishing on the publish instance.  We got to work after we import the forms on both the Author and the...

We've resolved the anonymous access issue.  Author and Publish were both using port 443, we thought that by using a combination of hostname + port AEM would be able to distinguish between the two instances but that's not the case.  We resolved the issue by assigning the Author instance to port 444 a...

we are using the publish instance to publish our content.