Nope, looks like it’s a random error, always the hardest to diagnose, but we definitely continue to experience it. It’s possible it’s a back-end cache issue on the WPEngine side, as the page noted above was excluded from their cache (by their admins…I have no control over this, vs. other caches I’ve worked with) and it consistently loads, though with all other pages (e.g., this one I just did to test, using exact same mashup code as the one above) it seems necessary that they are invoked via https:// (i.e., avoiding their cache) vs. desired http:// in order to load correctly.
Thanks again for your input.
Regards,
Jim P.