The exact same call to Actions.getPageUrl will 4/5 times return correctly. But the other 1/5 times all I get back is an empty result. This happens without any paramters being changed.
When the Empty Response happens, there’s no error message displayed, logged to error_log, or anywhere else that I can find. I don’t have any idea how to proceed with debugging this issue.’
Can I turn on more verbose debugging some how?
Lastly, I am not able to reproduce this issue on the demo site.
[ol]
[li] Changing the period parameter from period=2001-01-01,today to period=2013-05-01,today causes the occurence rate of the empty set response to decrease dramatically (to approximately 1/50 requests). However, the problem still occurs.
[/li][li] I have discovered the log_messages config directive, and have captured two logs. One for a successful response, and one for when the empty set is returned. They’re included in pastebin links below.
[/li][/ol]
I had not disabled browser triggered archiving. I didn’t expect API requests to count as a ‘browser trigger’.
This morning I disabled browser triggered archiving and it appears that when I ran the cron task, it happened to result in one of the empty set responses, which was then cached. So EVERY Request was coming back as an empty set.
Without waiting for the timeout to expire, the only way I could get an expected (non-empty set) result was to re-enable browser triggered archiving.
So caching isn’t going to fix this problem for me. I really need to figure out why the exact-same query sometimes results in a [ ] response.