Adobe Sign scheduler not running on publish instance in AEM 6.5 adaptive forms
In AEM v6.5 Adaptive Forms, the Adobe Sign status scheduler periodically checks the status of Adobe Sign agreements. These updates are essential because once an agreement is marked as complete, the configured submit actions on the adaptive form are triggered. This article considers the scenario where the submit action is set to send emails upon form submission. This happens due to design limitations and configuration mismatches. To fix this, configure reverse replication, verify environment settings, and follow best practices to ensure the scheduler functions as intended.
Description description
Environment
Product: Adobe Experience Manager (AEM) Managed Services Support
Version: AEM v6.5 Forms
Instances: Production and Stage setups
Issue/Symptoms
-
The Adobe Sign integration works correctly on both Author and Publish instances for initial form submission and email prompts.
-
On the Author instance, the Adobe Sign status scheduler sends follow-up emails with signed documents as expected.
-
On the Publish instance:
- The scheduler doesn’t execute, even after modifying its cron expression to run every 5 minutes.
- Logs display the message:
Not running Adobe Sign scheduler on publish instance. - Reverse replication errors prevent agreement status updates from syncing between Publish and Author environments.
Resolution resolution
The Adobe Sign status scheduler is designed to run only on Author instances to centralize agreement processing and avoid conflicts in multi-node Publish setups. Follow these steps to resolve the issue:
-
The scheduler is restricted to Author environments. It syncs agreement statuses like SIGNED and sends follow-up emails with signed documents.
-
Set up reverse replication agents to replicate agreement data from Publish to Author:
-
On Publish:
- Set up an Outbox agent with a transport URI pointing to
repo://var/replication/outbox. - Disable Use for reverse replication in the agent settings.
- Use valid credentials.
- Set up an Outbox agent with a transport URI pointing to
-
On Author:
- Configure a Reverse Replication agent pointing to the Outbox path of the Publish server.
-
-
Ensure all instances (Author, Pub1, Pub2) use identical Adobe Sign integration settings—OAuth URLs, access token URLs, client IDs, and secrets.
-
Confirm that replicated nodes reflect accurate statuses. Nodes should transition from
OUT_FOR_SIGNATUREtoSIGNEDonce agreements are completed. -
If issues persist:
- Restart relevant bundles or servers (preferably in non-production environments).
- Enable debug logs temporarily to identify root causes.
-
Always take a working backup of your instances before making any configuration changes.