In the first post about Splunk Cloud Gateway I talked about not being able to use Saved Searches with the Splunk Cloud Gateway. I worked with Splunk and got the official response back about the issue.
So you discovered a bug! I will have a fix for this before the next release of the Cloud gateway app. The issue is with the name of the saved search. We are not url encoding the ref string when we should be which is causing the parser to fail. If you want to work around this issue use a name for the saved search that doesn’t have any spaces.
After working with Splunk, I can confirm that this works. Using camel case (CamelCaseWorks) is a great way to accomplish this without spaces.