Splunk Enterprise Security

How we can debug reason="Could not get next runtime in corrrelation search to raise an alerts ?

AL3Z
Builder

Hi,
My cs is not raising an alerts, when I search index=_internal sourcetype=scheduler "xyz- CS" log_level=INFO

07-14-2023 12:50:00.552 +0000 INFO SavedSplunker - savedsearch_id="nobody;SplunkEnterpriseSecuritySuite;Audit - CP - PDM Uploads Non Colgate instances - Rule", search_type="scheduled", user="abc", app="SplunkEnterpriseSecuritySuite", savedsearch_name="xyz- CS - Rule", priority=default, status=continued, reason="Could not get next runtime", scheduled_time=0, window_time=-1

Labels (1)
0 Karma
Get Updates on the Splunk Community!

Accelerating Observability as Code with the Splunk AI Assistant

We’ve seen in previous posts what Observability as Code (OaC) is and how it’s now essential for managing ...

Integrating Splunk Search API and Quarto to Create Reproducible Investigation ...

 Splunk is More Than Just the Web Console For Digital Forensics and Incident Response (DFIR) practitioners, ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...