Documentation

Report sending functionality not working in Campaign Standard post-upgrade

Last update: Thu Sep 25 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

If you encounter issues in Adobe Campaign Standard (ACS) where hourly scheduled reports fail to send post upgrade, review reportSending workflow logs for errors and ensure that the Starting On timestamp for scheduled tasks aligns with the the workflow’s execution interval.

Description description

Environment

  • Product: Adobe Campaign Standard (ACS)
  • Instance: Development and production environments following an upgrade to versions 22.3 through 25.2

Issue/Symptoms

Campaign Standard successfully delivers daily scheduled reports, but fails to send hourly scheduled reports. The reportSending workflow logs show errors when scheduled reports fail to send.

The issue occurs due to the Scheduled Report functionality for hourly reports not working as expected, and because the out-of-the-boxreportSending workflow doesn’t pick up hourly scheduled reports.

Resolution resolution

To resolve issues with the report sending functionality in ACS, follow these steps:

  1. Restart services daily after any upgrade. This often resolves unexpected behaviors without requiring configuration changes.

  2. Check that the reportSending workflow is functioning correctly by reviewing its logs.

  3. Go to  Administration  >   Application settings  and validate that the xtkOption FEATUREFLAG_REPORTSHARE_HOUR is set to 0.

  4. Ensure that the Starting On  timestamp for scheduled tasks aligns with the reportSending workflow’s execution interval.

    • The workflow runs at fixed intervals, typically every hour at 00 minutes (for example, 6:00 PM, 7:00 PM). It checks for scheduled tasks at its next execution time. If the Starting On  time is set in the past or too close to the next execution time, the task may be skipped or not processed.

    • As best practice, always set the Starting On  time to a future hour that matches the workflow’s execution pattern. This ensures the workflow can properly queue and process the scheduled send without missing it due to timing mismatches.

    • For example, if you edit a project at 5:10 PM and want it to be processed soon, set the Starting On  time to 7:00 PM. The workflow will run at 6:00 PM, detect the new schedule, and prepare to send at 7:00 PM.

      Sample scenario:

      table 0-row-4 1-row-4 2-row-4
      Scheduling Time Recommended Starting On Time Workflow Execution Time Result
      5:10 PM 7:00 PM 6:00 PM Schedule picked up
      5:10 PM 6:00 PM 6:00 PM May be skipped

    • For hourly schedules, update the Starting On  timestamp to the top of the hour, ideally to the nearest hour plus two hours.

  5. After updating the schedule, confirm that emails are being sent successfully.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f