Using the transaction command twice in a search

[Dark_Ichigo]

I have tried over and over to apply two transaction commands to my search each with a different Field and it will show that I do have 17 or 18 matching results but it just wont display them!, I dont think Splunk supports Multiple transaction commands in a search.

I have taken a look at the following previous asked question: Connecting-Two-Transaction and it seems no one was able to solve the issue!, I even tried the "keeporphans=true" with the transaction command and yet it shows that there are hundreds of matching results but it just wont display them!

[las]

I didn't get the trick with adding a max to work alone, but when I added "| eval _txn_orphan=NULL" just before my second transaction it works like a charm.
I haven't tried without the max's.

[bbingham]

I have a core bug opened on this issue, if you add in "max"'s you'll get your events to show, such as "maxspan=2" "maxevents=15". You can also pipe to a stats values(_raw) and you'll see your events. Let me know if you'd like the SPL for the issue.

Make sure all "transactions" in the search have max's specified.

[Dark_Ichigo]

I didnt want to use the transaction command twice in the first place, but I was forced to find a workaround due to the subsearch timing out issues that sadly splunk will not fix, even after setting the limits.conf to the Maximum for each subsearch stanza.

But if these both dont work, whats the point of trying any more if I cant find an alternative solution?

[Ayn]

I know for sure that I've used multiple transactions in searches with success a number of times. Do you have a specific issue? It's hard to solve the problem you're having without knowing any details about it 🙂