Adrian Simpkins Posted August 20, 2024 Posted August 20, 2024 Hi All I have had a few colleagues report an issue with the connection functionality this morning. In a number of our scripts we connect users as required - this morning I am seeing a number of failed connections even though nothing has changed in the BPMs - anyone else seeing issues this morning please? Many thanks Adrian
Nanette Posted August 20, 2024 Posted August 20, 2024 @Adrian Simpkins please can you provide a copy of the failure/error?
Adrian Simpkins Posted August 20, 2024 Author Posted August 20, 2024 Hi Nanette - error below - I have tried removing and readding the connected person and restarted the script but this has only fixed one of the requests. I have just run the failed request report again and I have 30 new failures since I ran it this morning just after 7am I will raise in a support call now Many thanks
Nanette Posted August 20, 2024 Posted August 20, 2024 @Adrian Simpkins@will.good thank you we have identified an issue and I are working on a fix with the highest priority. Please bear with us. 1
Peter Clough Posted August 20, 2024 Posted August 20, 2024 Also affecting us. I made the mistake of re-opening Edge, now get this on login through SSO: Error An error occurred initializing the framework. unauthenticated
Gareth Cantrell Posted August 20, 2024 Posted August 20, 2024 We are also seeing SSO issues - none of our users can login I logged out to verify the issue and can no longer get back in either. I've raised an emergency issue for this already
danb Posted August 20, 2024 Posted August 20, 2024 Just now, Gareth Cantrell said: We are also seeing SSO issues - none of our users can login I logged out to verify the issue and can no longer get back in either. I've raised an emergency issue for this already ive done the same too
Berto2002 Posted August 20, 2024 Posted August 20, 2024 Yes we've raised a premier support for this But a subset of our users are in and working as normal
Keith Stevenson Posted August 20, 2024 Posted August 20, 2024 All We have identified the root cause and a fix is being rolled out. We expect this to be completed within 10 minutes. Kind Regards
danb Posted August 20, 2024 Posted August 20, 2024 6 minutes ago, Keith Stevenson said: All We have identified the root cause and a fix is being rolled out. We expect this to be completed within 10 minutes. Kind Regards we are back in and working now
Keith Stevenson Posted August 20, 2024 Posted August 20, 2024 All The fix has been rolled out Kind Regards 1
Peter Clough Posted August 20, 2024 Posted August 20, 2024 As are we. Thanks for the rapid fix, @Nanette & @Keith Stevenson.
Sam P Posted August 20, 2024 Posted August 20, 2024 We are back online and unsure if this is related however I now have a workflow generating errors on a GetTimestamp node. I am unable to Restart the last step via the Request nor Resume process from the Failed/Cancelled list. No changes have been made to the workflow for a few weeks and has been working fine until today
Keith Stevenson Posted August 20, 2024 Posted August 20, 2024 @Sam P The above thread got hijacked. We have fixed a number of flowcode nodes , sadly getTimeStamp has not been completed yet but is currently being worked on. That will be patched shortly and will reply once done Kind Regards 1
Sam P Posted August 20, 2024 Posted August 20, 2024 Thank you, I will wait patiently thanks for keeping us updated
Akin A Posted August 20, 2024 Posted August 20, 2024 We are experiencing the same error with one of our workflows and it's still happening.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now