Issue with Cron Triggers in JCASC Jobs

It sounds like your cron triggers only kick in after a manual run. This happens because Jenkins doesn't start the cron schedule until the job runs at least once.

Workarounds:

• Use a Groovy script in the Script Console to trigger jobs right after creation.
• If you're using Job DSL, add a step to automatically trigger the job after it's created.
• You could also try poll SCM as an alternative trigger to avoid manual runs.

If you’re using other specific plugins or have more details, feel free to share. It could help refine the solution!