Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-629

*MISSING_TOKEN* status leading to a incorrect "Domain already verified" error

    • 10
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Summary

      The domain verification status is MISSING_TOKEN and when the users try to verify the domain again it shows the following message:

      Which does not have any link to the status MISSING_TOKEN that is usually triggered when there is an issue to maintain/confirm the domain claim.

      Steps to Reproduce

      Unknown

      Expected Results

      Either that error should not be displayed or the status of the domain verification should be different.

      Solution / Workaround

      No current workaround but disregard the error message and verify the domain.

              gvenkatesh@atlassian.com Gautam Venkatesh
              jnunes@atlassian.com João Nunes
              Votes:
              0 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: