Sling Job Disappearing Without Execution on AEM as Cloud Service

[mayank0928]

Hi Everyone,

I'm experiencing an issue related to Sling Jobs in AEM as Cloud Service.

• I have a scheduler set up to trigger an archive Sling job.
• When the job is triggered, the corresponding job node gets created in /var/eventing. However, almost immediately after its creation, the job node disappears without any traces of execution.
• There are no exceptions or errors logged in the system.
• I have observed that the creation and finish dates of the job are almost identical (refer to the attached screenshot for details).
• The scheduler is configured to run exclusively on the Leader Node, ruling out potential complications from a distributed cluster setup in AEMACS.
• Interestingly, the same job executes and completes without issues when triggered by an Event listener.

Could anyone please assist or provide any suggestions for the above?

@kautuk_sahni @arunpatidar 

[joerghoh]

If you can rule any complication from the cluster, can you replicate that behavior with the SDK on your local machine?

[mayank0928]

Hi @joerghoh

Thanks for your reply..

But, I am not being able to replicate with my local instance, it works perfectly fine over there. It only comes in Dev or Any other Cloud Environment.

[Jörg_Hoh · Accepted solution]

That's indeed an interesting case, but I have to point you to the official support channels for that.

(Drop me the ticket ID in private, I will try to have a look at it.)

Jörg