I found this error in Scheduler.log.
I was trying to send an email in an alert.
07-07-2016 06:29:06.697 -0300 INFO SavedSplunker - savedsearch_id="admin;search;lab_real 1", user="admin", app="search", savedsearch_name="lab_real 1", status=skipped, reason="maxconcurrent limit reached", scheduled_time=1467883740, window_time=0
Thank you!!
This is related to max concurrent search quota being reached for the user. See these for more info
http://wiki.splunk.com/Community:TroubleshootingSearchQuotas
https://answers.splunk.com/answers/54674/how-to-increase-the-maximum-number-of-concurrent-historical...
This is related to max concurrent search quota being reached for the user. See these for more info
http://wiki.splunk.com/Community:TroubleshootingSearchQuotas
https://answers.splunk.com/answers/54674/how-to-increase-the-maximum-number-of-concurrent-historical...
We started seeing this after we recently upgraded to 6.4.2, but not before. Is there any correlation between the two?