Server-side event trigger not firing for scheduled events in AEC 2023

CRM Adobe Experience Cloud
, , , , , , , ,
1

We’ve configured scheduled events in our Event Management module to trigger server-side workflows, but the triggers are not firing at all. The event scheduling configuration appears correct in the admin console, and the events are created successfully. However, when I check the event logging, there’s no indication that the trigger job is even attempting to execute.

Here’s our current trigger configuration:

event.trigger.enabled=true
event.schedule.jobInterval=300000
event.trigger.serverSide=true

The scheduled events show as “Pending” in the dashboard but never transition to “Triggered” status. We’ve verified the trigger job enablement settings are active, but something is preventing the server-side execution. Is there a specific service or background process that needs to be running? Our event logging shows event creation but no trigger attempts. Any insights would be appreciated.

system 2

I can help you resolve this comprehensively. Based on your configuration and symptoms, you’re dealing with three interconnected issues related to event scheduling config, trigger job enablement, and event logging.

Event Scheduling Configuration Issue: Your properties are correct but incomplete. You need to add the scheduler activation flag:

event.trigger.enabled=true
event.schedule.jobInterval=300000
event.trigger.serverSide=true
event.scheduler.active=true
event.scheduler.startDelay=60000

The missing event.scheduler.active flag prevents the scheduler from initializing, and startDelay ensures proper startup sequencing.

Trigger Job Enablement: Verify your services configuration includes the EventTriggerJobProcessor. In your services.xml, ensure:

<service name="EventTriggerJobProcessor" enabled="true">
  <property name="poolSize" value="5"/>
  <property name="queueCapacity" value="100"/>
</service>

If this service is disabled or missing, triggers won’t execute. The poolSize should match your expected concurrent event volume.

Event Logging Deep Dive: Enable verbose event logging to see what’s actually happening:

log4j.logger.com.adobe.event.trigger=DEBUG
log4j.logger.com.adobe.event.scheduler=DEBUG

With verbose logging, you’ll see messages like “EventScheduler initialized”, “Job queue processing started”, and individual trigger execution attempts. The absence of these messages confirms the scheduler isn’t running.

Additional Critical Checks:

  1. Verify the background job executor thread pool isn’t exhausted (check thread dumps)
  2. Ensure no maintenance mode flags are active that would suspend job processing
  3. Confirm the service account has execute permissions on event trigger handlers
  4. Check that events have the triggerType="SCHEDULED" attribute set correctly

Verification Steps: After applying these changes:

  1. Restart your AEC instance to reinitialize services
  2. Monitor logs for “EventScheduler started successfully” message
  3. Create a test scheduled event with a short interval (60 seconds)
  4. Watch logs for “Processing scheduled event trigger” entries
  5. Verify event status transitions from Pending → Triggered → Completed

The root cause is almost certainly the missing scheduler activation combined with insufficient logging visibility. Once you enable the scheduler properly and turn on verbose logging, you should see trigger execution begin within your configured job interval. If issues persist after these changes, share your verbose logs and I can help identify any remaining configuration gaps.

This draft is based on general Adobe Experience Cloud knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.

3

I’ve seen similar behavior when the event scheduler service isn’t properly started. Can you verify that the EventSchedulerService is running in your server logs? Also check if there are any exceptions during server startup related to job initialization.

4

This looks like a classic case of the trigger job not being enabled at the service level. The configuration properties you’ve set are correct, but you also need to ensure the background job processor is active. Check your services.xml file to confirm that the EventTriggerJobProcessor is registered and not disabled. Additionally, verify that your server has sufficient thread pool allocation for background jobs. I had a similar issue where the job pool was exhausted by other processes, preventing event triggers from executing. Look for any thread starvation warnings in your logs around the scheduled execution times.

5

Have you checked the event trigger permissions? Sometimes the service account running the scheduler doesn’t have execute permissions on the trigger handlers. Also worth checking if your event definitions have the correct trigger action mappings configured.

6

I encountered this exact problem last month. In my case, the issue was twofold: first, the event logging level was set too low to capture trigger attempts, which made debugging difficult. Second, the trigger job interval was conflicting with our system maintenance window. When I examined the detailed event logs after enabling verbose logging, I discovered that the jobs were being queued but immediately cancelled due to a maintenance mode flag that was inadvertently left active. Check your system status flags and ensure maintenance mode isn’t interfering. Also, try reducing your jobInterval temporarily to see if timing is a factor. The 300000ms interval might be too long for initial testing.

8

Can you share what’s in your event logging output? Even if it’s not showing trigger attempts, there might be initialization errors or configuration warnings that would help diagnose this. Also check if the events are being created with the correct trigger type attribute.

9

Another thing to verify is whether your scheduled events have the proper execution context set. I’ve seen cases where events created through the API lack the necessary context metadata that the trigger job processor expects, causing them to be skipped silently during job execution cycles.