Skip to content

Brynn Staples

My feedback

3 results found

  1. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Brynn Staples shared this idea  · 
  2. 53 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Brynn Staples supported this idea  · 
  3. 128 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    As part of the investigation into the cause of this issue, we personally reached out to many of you over email. We have so far heard from only some of you.

    Of the responses we have received, the conclusion we’ve come to is:
    This issue was intermittent, happened once during the course of work but somehow got resolved and has not happened again. This issue can’t be reproduced now.

    Over a period of time, this thread has not thrown any fresh clues on why this issue seems to occur randomly for some and then seems to resolve itself. So we’re closing this thread.

    However, even though we’re closing this thread, if you again run into this issue any time on a consistent basis, please report it here on UserVoice (in a new thread) with supporting assets like:
    A) a test file,
    B) detailed steps to replicate the issue
    C) any…

    Brynn Staples supported this idea  · 

Feedback and Knowledge Base