Cronicle API: create_event creates wrong timings

[ContainerCat]

Summary

I am using a curl call to create an event. In the docs, I read the following: "Each property should be an array of numerical values. If omitted, it means the same as "all" in that category (i.e. asterisk * in Cron syntax)" (https://github.com/jhuckaby/Cronicle/blob/master/docs/APIReference.md#event-timing-object). So i thought, if I do not give up my timings, it will run every minute of every hour of every day, etc. Instead, it creates an on demand event. I would like a way to create an * * * * * event without having to specify every "time"

Steps to reproduce the problem

Perform a curl call to the cronicle: curl https://$CRONICLE_HOSTNAME/api/app/create_event/v1
-X POST
-H "Content-Type: application/json"
--data '{ "title": "'$CRON_IDENTIFIER'", "category": "general", "enabled": 1, "plugin": "shellplug", "target": "'$CRONICLE_HOSTNAME'", "session_id": "'$session_id'" }'

Your Setup

NA, but: Cronicle on Kubernetes with Loadbalancer

Operating system and version?

NA, but: Ubuntu 22.04.4

Node.js version?

v20.17.0

Cronicle software version?

Version 0.9.59

Are you using a multi-server setup, or just a single server?

single server

Are you using the filesystem as back-end storage, or S3/Couchbase?

filesystem

Can you reproduce the crash consistently?

NA

Log Excerpts

NA