https://community.splunk.com/t5/Random/Known-issue/m-p/248390#M1140 <P>Hi,</P> <P>I't could be possible to get more information about this issue? SPL-98594</P> <P>Thanks,</P> Tue, 15 Mar 2016 11:53:42 GMT jmallorquin 2016-03-15T11:53:42Z https://community.splunk.com/t5/Random/Known-issue/m-p/248390#M1140 <P>Hi,</P> <P>I't could be possible to get more information about this issue? SPL-98594</P> <P>Thanks,</P> Tue, 15 Mar 2016 11:53:42 GMT https://community.splunk.com/t5/Random/Known-issue/m-p/248390#M1140 jmallorquin 2016-03-15T11:53:42Z https://community.splunk.com/t5/Random/Known-issue/m-p/248391#M1141 <P>According to the <A href="http://docs.splunk.com/Documentation/Splunk/latest/ReleaseNotes/KnownIssues">known issues</A> list, this particular known issue relates to event routing to multiple targets. I'd recommend opening a case with Splunk Enterprise Support if you think you're being affected by this issue. If not, just post whatever your problem is and perhaps we can assist.</P> Tue, 15 Mar 2016 12:15:38 GMT https://community.splunk.com/t5/Random/Known-issue/m-p/248391#M1141 lcrielaa 2016-03-15T12:15:38Z https://community.splunk.com/t5/Random/Known-issue/m-p/248392#M1142 <P>Ok, </P> <P>Thanks,</P> Tue, 15 Mar 2016 13:28:20 GMT https://community.splunk.com/t5/Random/Known-issue/m-p/248392#M1142 jmallorquin 2016-03-15T13:28:20Z