DocumentationExperience Cloud KCS

AEM as a Cloud Service: Benign ERROR log entries for Forms Portal Sign Scheduler and Content Backflow Cleanup

Last update: September 1, 2026

This article explains why recurring ERROR-level log entries for the Forms Portal Sign Scheduler and Content Backflow Cleanup jobs appear in AEM Cloud Service Sites environments and clarifies that these entries are benign and require no action.

Description description

Environment

Adobe Experience Manager as a Cloud Service (Sites) (all versions)

Issue/Symptoms

Two recurring, unrelated ERROR-level log entries appear on Author instances:

  • Forms Portal Sign Scheduler

    • Log entry: com.adobe.fd.fp.impl.external.SignStatusHandlerImpl [ FP] [ Sign Scheduler] Forms Portal USC Configuration is not configured
    • Occurs daily at midnight from thread com/adobe/aem/adobesign/statusupdate/scheduler.
    • Environment: All tiers (Dev, Stage, Prod).
    • Context: Adobe Sign / Forms Portal is not used, and Unified Storage Connector (USC) is intentionally not configured.

  • Content Backflow Cleanup Job

    • Log entry: com.adobe.aem.contentbackflow.utils.CleanupSlingJobs got RepositoryException in cleanupEmptyFolders

    • Variants include:

      • Node with path /var/eventing/jobs//com.adobe.aem.contentbackflow.import.job does not exist.
      • OakAccess0000: Access denied

    • Occurs daily at 03:00.

    • Environment: Only on Dev and Stage Author (content backflow import targets), not on Prod Author (backflow source).

    • Context: The cleanup routine iterates over job-type paths that do not exist or have restricted access.

Cause

Both log entries are the result of scheduled jobs reporting on absent or unconfigured components (Forms Portal USC, transient job nodes) and are not indicative of functional failures.

Resolution resolution

Follow these steps to resolve the issue:

  1. Provision an AEM as a Cloud Service Sites environment with multiple tiers (Dev, Stage, Prod) and configure Content Backflow in a top-down configuration (Prod → Stage → Dev).
  2. Do not configure Adobe Sign / Forms Portal USC.
  3. Wait for the daily scheduled jobs to run.
  4. Review the Author logs on each tier and confirm that the log entries match those described in this article and occur under the same conditions.
  5. For Forms Portal Sign Scheduler, treat the log entry as benign. When no USC configuration exists, the scheduler logs the message and exits without performing any further action.
  6. Do not attempt to disable only this scheduler because no supported OSGi configuration exists for that purpose.
  7. If the Forms add-on is not required for any functionality, remove it from the deployment to stop the scheduler. Otherwise, safely ignore the log entry or filter it through log configuration.
  8. Leave the Forms add-on in place unless all features in the environment confirm that they do not use it.
  9. For the Content Backflow Cleanup Job, treat the log entries as benign when the cleanup routine encounters non-existent or inaccessible job nodes.
  10. Safely ignore these log entries because they do not affect completion of the cleanup process or the functionality of Content Backflow.
  11. Do not make any customer-side configuration changes or take any additional action. Filter the log entries if desired.
  12. Verify that both log entries are benign and do not affect system functionality.
recommendation-more-help
experience-cloud-kcs-help-kbarticles