RTM API errors - testing a workaround

Heard of someone getting errors from the RTM API - I can’t recreate,
but at a guess, it might be because I’m sending multiple requests with
the same callback name. Switching the callback name to use an
incrementing number instead of the current time, to see if that
resolves it.