Reporting

scheduling report error

a212830
Champion

Hi,

I'm trying to schedule a report with the following cron config:

2-59/5 * * * *

When I try to save this, the "Edit Schedule" box says that I have an "Invalid cron". I know that this cron is valid. Any suggestions?

Tags (3)
0 Karma
1 Solution

gkanapathy
Splunk Employee
Splunk Employee

The cron is not valid. perhaps you mean:

2-59/5 * * * *

View solution in original post

gkanapathy
Splunk Employee
Splunk Employee

The cron is not valid. perhaps you mean:

2-59/5 * * * *

a212830
Champion

Turned out to be a bug - you can enter the cron entry via searches-reports and it will work.

0 Karma

danielrusso1
Path Finder

a212830 can you elaborate? I'm having the same issue. When you say you can enter the cron entry via searches-reports, what do you mean?

0 Karma

a212830
Champion

Yes, it's correct. Going to open a ticket on it...

0 Karma

somesoni2
Revered Legend

Just ensure spacing is correct. 2(no space)-(no space)59(no space)/(no space)5(1 space)(1 space)(1 space)(1 space)

0 Karma

a212830
Champion

Sorry, yes, I do, but I still get the same error.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...