Jetpack Manual Publicize server down

Update #2 – It’s now 1:41am and I continue to re-test. I have gotten my social media to go out on the manual publish, it just started working, but the subscriptions still haven’t worked yet. I wish a Jetpack person would respond on this? I really do think this is their server issues, especially because I’m doing this manually and not using any scheduled stuff that I know is not working still…

Update #3 – 09:30am – The manual publish finally went through this morning with both my social media and with my subscriptions. I don’t know what happened that caused it to not work last night, but at least for now it appears to be working. Maybe Jetpack will chime in here to look at their logs and see what happened with their publicize server last night?

The manual publish finally went through this morning with both my social media and with my subscriptions. I don’t know what happened that caused it to not work last night, but at least for now it appears to be working. Maybe Jetpack will chime in here to look at their logs and see what happened with their publicize server last night?

The problem wasn’t with our servers; if Publicize and Subscriptions were delayed on your site, it’s because your site wasn’t able to synchronize the new post back to WordPress.com for a bit due to a lag with the synchonization process on your site.

As we’ve seen in the past, this does sometimes happen on your site because of limited resources.

If it keeps happening, I would recommend switching to a different hosting provider, as those issues have been impacting your site quite often in the past few months.

P.S.: I see you also contacted us via email about this; I closed the ticket to avoid duplicated replies about this issue.

@jeherve

When you say limited resources I’m assuming you don’t mean with my actual site but with the domain provider not having enough resources to dedicate to the process of completing my posting?

If that were so, why would it be then that my post when I manually hit the publish, that it immediately went up onto the actual site, meaning it for posted right away. As When I have seen lags or issues with resources with GoDaddy’s Managed WordPress in the past, once I hit publish that the bar would slowly move across the top of my URL line. Or I would see connection issues with the sharing tab for social media or various other indicators that showed it was my provider. But everything was running blazing face that night in all circumstances Jeremy. And to be honest, this has only ever happened once before in the past four years of having my publicize with Jetpack and then too you said it wasn’t your servers but yet eventually I got a response from your email support staff that found it really was your servers and that it was just a quick hiccup that lasted just under 24 hours?

Regardless, my question still stands then that if you are 100 percent sure that it wasn’t your servers that were too inundated to complete the publicize and that it wasn’t my site itself, but really resources with GoDaddy, how do you really prove something like this when everything else is showing fine to be working in speed and there are no delays anywhere else? As I already said, GoDaddy wasn’t having any issues that night either from what I could tell and I know it wasn’t my actual site because I hadn’t changed anything to have caused the one 9 hour long issue.

And just to clarify as well, when I hit the manual publish button, as soon as my post hits my site, doesn’t the request immediately go to Jetpack’s servers to be processed to complete the publicize? I say this because initially the social media started working at about 2 hours into it, but not the email part, and eventually after sleeping it off for a few hours, the email part did too. Are these two different parts of a process and two different servers on your end to handle those parts of the publicize? Why would part of it work and then the other part later?

To make a blanket call that it’s GoDaddy for an issue that only happened once before that was indeed once before a Jetpack confirmed server issue doesn’t help me to diagnose the issue and think about switching. I indeeed haven’t had really any GoDaddy issues in recent months with my site but maybe once and really it’s only been the caching issue with scheduled blogs that has ever been the nuisance I have with them.

I hope you will take the time to respond in more depth here because I really want to get to the bottom of where this failed for those 9 hours, why it was a partial fail with social media working after a small bit then eventually the email part, and how could I even prove it might have been GoDaddy when all else was working blazing face that night.

• This reply was modified 8 years, 1 month ago by Andrew Arthur Dawson.

When you say limited resources I’m assuming you don’t mean with my actual site but with the domain provider not having enough resources to dedicate to the process of completing my posting?

You may be able to publish posts on your site without any issues; your WordPress installation just ran into some problems when it had to complete one or more scheduled jobs after the post was published.

In our case, that scheduled job was sending data from your site to an external service, WordPress.com.

when I hit the manual publish button, as soon as my post hits my site, doesn’t the request immediately go to Jetpack’s servers to be processed to complete the publicize?

That’s the expected behaviour, and that’s what happens unless the sync job can’t start on your site.

I can’t tell you why that job couldn’t start on your site, though; I can only tell you that it didn’t. We unfortunately don’t have any more information about the issue, as the synchronization process starts on your site.