Find a bug in FindTime?

Unable to login to findtime, or create a meeting invite

Unable to login to findtime, or create a meeting invite

38 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Ramkumar DevanathanRamkumar Devanathan shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    completed  ·  Chris HoornAdminChris Hoorn (Product Engineer, FindTime) responded  · 

    The issue should be resolved. If you experience any further authentication issues, please use the “Sign in” link on the FindTime homepage (findtime.microsoft.com). If you still experience an error, you may also need to clear your browser cache.
    We deeply regret any inconvenience this is sure to have caused.

    Thanks for being patient with us.

    36 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Chris LewisChris Lewis commented  ·   ·  Flag as inappropriate

        Currently, FindTime still works since it's installed into my Outlook...but it looks like it's on the way out. When I go to FindTime.microsoft.com and click the install button, this pops up:

        Important News about FindTime

        Since we launched FindTime in late 2015, we've seen millions of votes to find the best day and time to meet. Today we are sharing news that FindTime is no longer available to install as an Outlook add-in.

        If you're an existing FindTime user, you'll be able to continue using FindTime. You'll be notified before we make any changes to the add-in.

        What's next?
        We are still committed to helping you save time when scheduling meetings and will have exciting news to share soon.

      • Ian CaldwellIan Caldwell commented  ·   ·  Flag as inappropriate

        argh, what happened to FindTime over the summer? this was becoming a major hit at my office, got some very confused people now.

      • Anonymous commented  ·   ·  Flag as inappropriate

        WTF Chris Hoorn, how can you guys just remove a product with no warning that your paying subscribers use every day. It was just a few months ago that you touted how many meeting polls were created. We deserve more than just "We are still committed to helping you save time when scheduling meetings and will have exciting news to share soon."

      • Anonymous commented  ·   ·  Flag as inappropriate

        i can log in, see meeting and availability, but when I click "schedule" I get the following error: "Something broke. We were unable to schedule this invite because your credentials have expired. Please sign in and try again."

      • Chad D.Chad D. commented  ·   ·  Flag as inappropriate

        Any chance of getting this fixed?

        Oh no! We hit an error.

        AADSTS70002: Error validating credentials. AADSTS50012: Client assertion contains an invalid signature. [Reason - The key was not found., Thumbprint of key used by client: 'B81EE41402A5796ED02585ED4FAE7D75B16B9888', Configured keys: [Key0:Start=07/07/2015, End=07/06/2017, Thumbprint=5F60876FD70A872475361FB08490D1EA2ED9E324;Key1:Start=01/08/2015, End=01/07/2017, Thumbprint=BE201643E15E5817BDD038230EA07B5BA0058E88;]]Trace ID: 3626ec7d-5f53-4a4b-926c-f6e7d4e34200Correlation ID: 0bd13267-dfc2-43d8-a...

      • ChrisChris commented  ·   ·  Flag as inappropriate

        Please offer an update on this, if the issue is going to be resolved then I'll wait. With the application removed from the store I'm wondering if I should evaluate other tools? If it's the latter I'm ok, I just need to know.

      • TonyTony commented  ·   ·  Flag as inappropriate

        72+ hours outage. Are there plans to bring it back?
        Is this a production application?

      • Rod VenemRod Venem commented  ·   ·  Flag as inappropriate

        I am receiving the following:

        "We are having trouble signing you in. Please close the add-in and try again.

        If the issue persists, please see our help page. If you are still unable to resolve the issue, send us a ticket and give us the error message in the popup (if any) and this reference ID:

        a293ca4e-bdef-4933-bccb-cf3a0266e84e"

      • AgostinoAgostino commented  ·   ·  Flag as inappropriate

        Some news? I know it's obvious... but have you double checked your Azure integration certificates.

      • ScottScott commented  ·   ·  Flag as inappropriate

        Seems FindTime is still down. Desperately need to get up and running to schedule a meeting with stakeholders this morning (Aussie time).

        Please advise.

      • Emma FranklinEmma Franklin commented  ·   ·  Flag as inappropriate

        But what is a "KEY" and how do I get a new one, since mine expired? So frustrating! And the irony of how much freaking time I've spent on this is not wasted on me every time I try to launch it again and see that tag "Time is of the essence!"

      • sean.caseysean.casey commented  ·   ·  Flag as inappropriate

        Hi, i'm getting error messages when i try to use FindTime. When I try to log into my dashboard via Chrome version Version 59.0.3071.115 (Official Build) (64-bit)
        at this site
        https://findtime.microsoft.com/home/dashboardlogin?loginId=05b8c579559c4e15b1f509eccdc1c283

        I get this error message: Oh no! We hit an error.
        AADSTS70002: Error validating credentials. AADSTS50012: Client assertion contains an invalid signature. [Reason - The key used is expired., Thumbprint of key used by client: '5F60876FD70A872475361FB08490D1EA2ED9E324', Found key 'Start=07/07/2015, End=07/06/2017, Thumbprint=5F60876FD70A872475361FB08490D1EA2ED9E324', Configured keys: [Key0:Start=07/07/2015, End=07/06/2017, Thumbprint=5F60876FD70A872475361FB08490D1EA2ED9E324;Key1:Start=01/08/2015, End=01/07/2017, Thumbprint=BE201643E15E5817BDD03823...

      • Vianne GreekVianne Greek commented  ·   ·  Flag as inappropriate

        I got this same error today.

        I went to findtime.microsoft.com and tried logging in there, and got the following message: AADSTS70002: Error validating credentials. AADSTS50012: Client assertion contains an invalid signature. [Reason - The key used is expired., Thumbprint of key used by client: '5F60876FD70A872475361FB08490D1EA2ED9E324', Found key 'Start=07/07/2015, End=07/06/2017, Thumbprint=5F60876FD70A872475361FB08490D1EA2ED9E324', Configured keys: [Key0:Start=07/07/2015, End=07/06/2017, Thumbprint=5F60876FD70A872475361FB08490D1EA2ED9E324;Key1:Start=01/08/2015, End=01/07/2017, Thumbprint=BE201643E15E5817BDD03823...

        It looks like my "KEY" expired 07/06/2017 - so... YESTERDAY. I suspect that's why it won't work in Outlook.

        I also saw a note where they said they are deprecating it for the OWA experience but am not seeing FindTime in there at all.

      ← Previous 1

      Feedback and Knowledge Base