Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when returning to the migration DIY flow #96510

Closed
renatho opened this issue Nov 18, 2024 · 5 comments · Fixed by Automattic/jetpack#40270
Closed

Error when returning to the migration DIY flow #96510

renatho opened this issue Nov 18, 2024 · 5 comments · Fixed by Automattic/jetpack#40270
Assignees
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". [Experiment] AI labels added [Feature Group] Site Migration [Feature] Notifications Site notifications. [Feature] Site Migration Features related to site migrations to WPcom Groundskeeping Issues handled through Dotcom Groundskeeping rotations Needs triage Ticket needs to be triaged [Pri] High Address as soon as possible after BLOCKER issues [Status] Auto-allocated [Status] Escalated to Product Ambassadors [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts [Type] Bug When a feature is broken and / or not performing as intended

Comments

@renatho
Copy link
Contributor

renatho commented Nov 18, 2024

Quick summary

This error was originally reported in p7DVsv-lGw-p2#comment-51714 by @cuemarie.

When we choose the DIY flow and continue later, sometimes it gives an error "Getting the migration key". I didn't find the exact reason, but I recorded a video with the error coming from the API.

Screen.Recording.2024-11-18.at.15.49.29.mov

Steps to reproduce

  1. Start a migration choosing the "I'll do it myself" option in the "How do you want to migrate?" step. This can be done following the steps:
    1.1. Navigate to /start.
    1.2. Choose "Import existing content or website" in the goals step.
    1.3. Navigate through the flow, selecting to migrate from a WordPress site, and the "I'll do it myself" option.
  2. When you are in the migration instructions screen, close the window.
  3. Navigate to /sites.
  4. Click on the site with the pending migration.
  5. Click on "Start your migration".
  6. I didn't identify the best way to reproduce it, but as you can see in the video I sent, it worked the first time it was loaded, but it was broken after the refresh with the error 403 - "Sorry, you are not allowed to do that" coming from the API.

What you expected to happen

Return the key properly.

What actually happened

An error happened while fetching it from the API.

Impact

Some (< 50%)

Available workarounds?

No and the platform is unusable

If the above answer is "Yes...", outline the workaround.

No response

Platform (Simple and/or Atomic)

No response

Logs or notes

No response

@renatho renatho added [Type] Bug When a feature is broken and / or not performing as intended Needs triage Ticket needs to be triaged labels Nov 18, 2024
Copy link

OpenAI suggested the following labels for this issue:

  • [Feature Group] Site Migration: The issue directly relates to errors encountered during the site migration process using the DIY flow.
  • [Feature] Site Migration: This specific label pertains to the functionality and features surrounding the site migration process, which is central to the reported issue.
  • [Feature] Notifications: The error could potentially involve notifications that inform users about migration statuses, especially considering the described API error.

Copy link

Support References

This comment is automatically generated. Please do not edit it.

  • p7DVsv-lGw-p2#comment-51714

@github-actions github-actions bot added the Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". label Nov 18, 2024
@matticbot matticbot added the [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts label Nov 18, 2024
@sixhours
Copy link
Contributor

Added this to Serenity's board.

@sixhours
Copy link
Contributor

Reducing this to High priority since, out of the entire WP.com user base, it's going to apply to a relatively small number of people.

@sixhours sixhours added [Pri] High Address as soon as possible after BLOCKER issues and removed [Pri] BLOCKER Requires immediate attention. labels Nov 18, 2024
@sixhours sixhours moved this from Needs Triage to Triaged in Automattic Prioritization: The One Board ™ Nov 18, 2024
@sixhours
Copy link
Contributor

(I was also able to reproduce this.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". [Experiment] AI labels added [Feature Group] Site Migration [Feature] Notifications Site notifications. [Feature] Site Migration Features related to site migrations to WPcom Groundskeeping Issues handled through Dotcom Groundskeeping rotations Needs triage Ticket needs to be triaged [Pri] High Address as soon as possible after BLOCKER issues [Status] Auto-allocated [Status] Escalated to Product Ambassadors [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts [Type] Bug When a feature is broken and / or not performing as intended
Development

Successfully merging a pull request may close this issue.

4 participants