update this message -- we have had problems in another project with this (the PIU interrupt mechanism) that were caused not by a dead Relay session, but by a browser that was, for reasons we don't know, refusing to keep Wsapi's cookies.  We may eventually figure out how to do wsapi authentication without cookies (local storage with a token or something), but that's more than we want to tackle for a small population of potential browsers.  For now, we'll go live with this message.
when in production, it's important to use the new wsapi.cru.org url instead of wsapi.ccci.org.  This helps with browser cookie issues, as the cookies are no longer 'third party' cookies.

This doesn't seem to help everywhere; safari seems to sometimes still refuse wsapi's cookies, according to our experiences with the PIU interrupt.