Open joweber123 opened 3 years ago
This will also occur if when a site that does have backups reverts and goes Atomic again. When the site goes Atomic again, within a reasonable timeframe, it will have access to the previous backups available; however, they can't restore one immediately due to this.
We generally have to wait or perform a manual disconnect and reconnect to get it working faster.
I believe this message started appearing after we fixed another message that requested the user to supply credentials. Re: 6188-gh-Automattic/jpop-issues#issuecomment-734852170
It seems to be the default message when the backup backend is still provisioning.
I'm leaving this open here for now but we might need to move to the JPOP repo.
29656330-hc
A case of a user being confused by the wording on that screen: 30192050-hc
Perhaps some more appropriate text would be:
Jetpack Backups are being created.
This happens on newly created sites for the first 30mins to an hour. It's normal and Jetpack is working, it just doesn't have a backup yet.
I ran into this in 16821750-hc
I encountered this in 4466866-zen as well.
Ran into this here on a reverted then re-AT'd site: 4551054-zd-woothemes Manually dis/reconnected JP to resolve
Ran into this while doing team testing and was confused by the messaging of Jetpack connection failed. If possible, we should definitely change the wording/message.
Saw this again in this ticket - 5545762-zen
Support References
This comment is automatically generated. Please do not edit it.
7732457-zd-a8c 7766945-zd-a8c
7807155-zd-a8c
7816962-zd-a8c
When a site is taken from Simple to Atomic by clicking the Jetpack > Backup button, until the first backup is available, the user sees the message "Jetpack connection has failed".
Steps to reproduce the behavior
https://wordpress.com/settings/disconnect-site/siteaddress?type=down
What I expected to happen
While no backup is ready, I would expect the message to continue to say "Your first backup will be ready soon".
What actually happened
Jetpack is still connected to the site. It looks like the issue is that no live backups are on file yet. Once a full backup is ready, the normal backup screen begins to show.
Temporary Workaround
I have been able to resolve this issue by queuing a full backup and then triggering a full Jetpack sync.
Level of impact (Does it block purchases? Does it affect more than just one site?)
This appears to be affecting all users that go Atomic through activating a backup.
Video
https://user-images.githubusercontent.com/24914028/109756832-fc1b0800-7c2b-11eb-8da9-546a4e91f48d.mov