Yes that what i thought, but then it will block all other components on startup because its maybe running for 30 minutes. So no chance to do it this way. I have to create a new Service and trigger it by a custom scheduler. Thanks for all replies.

If want to achieve that the scheduler runs directly on statup/after deployment but it seems it just starting after 4 hours for the first time and after that every 4 hours. The problem is the scheduler pulls data into AEM and otherwise I have to wait 4 hours for the very first execution.So the compon...

@Component(enabled = true, immediate = true, metatype = true, label = "cron job",   description = "cron job ")@Service(value = Runnable.class)@Properties({   @Property(name = "scheduler.expression", value = "0 0/15 * * * ?", description = "Cron-job expression Ex: '0 0/15 * * * ?' for 15 Mins"),   @P...

I have an actual scheduler but it runs not on startup only after the 4 hours of waiting and I want it the be run immediately.What's that: tireDesignsFetchJobFactory.createJob()

Can you point me to an example?

Hi guys,is it possible to trigger a scheduler once after every deployment? So the regular schedule time is 4 hours, but it will took 4 hours for the first run.Any property to set?Br,Tim

I think its more a cross dependency issue with commons-io than an AEM problem.

I don't know it do run locally and does build also in another pipeline.the error occurs building on jenkins an artifact and fails with this message. It's a build process out of my control so I am not really able to reproduce it.

Yes that's all I found. Is there maybe another way? start a the same service for every domain with different configs, without duplicating the service with another name?GooglemapsService --> config.plGooglemapsService --> config.comGooglemapsService --> config.nl...

Thanks Ratna So there is really no possibility to create them during runtime? Maybe someone knows a little bit more?