Jump to content

CRITICAL - Issue after automated upgrade to build 2892


Recommended Posts

  • Replies 80
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

We have verified the fix resolves the issue being reported, we are just in the process of determining the fastest way to apply this, we are minutes away, thank you for your continued patience.  G

We have identified the problem which is currently being verified and we will be applying this as a hot-fix to effected instances in the next 15 minutes or so, we are working as fast as we possibly can

@Gerry Looks like the team were able to update us - this is now working for us, including changes. Thanks for your help with this.

Posted Images

@Lyonel I think the little refresh icon on each errored request only goes back one step, rather than restarts the whole thing.

I don't think there is a way to completely restart - I'd be very happy to be wrong here!

Link to post
Share on other sites

All,

There is nothing you need do to, I have been told we have now applied a hot fix to all affected instances, this issue should now be resolved,.  We remain on high alert and will be monitoring very closely in the coming hours. Please report any further issues encountered, we are continuing our testing and postmortem activities for the next couple of hours, I will continue to monitor this thread. 

Gerry

 

Link to post
Share on other sites
1 minute ago, BenKeeley said:

Hi,

Do we need to wait a certain amount of time for the hot fix to apply? We are still affected.

Thanks

 

Hi,

Same as us for some requests, and working ok for other requests.

Thanks,

Samuel

Link to post
Share on other sites
3 minutes ago, BenKeeley said:

Hi,

Do we need to wait a certain amount of time for the hot fix to apply? We are still affected.

Thanks

 

Ben,

Let me find out for you, hold on please.

Gerry

Link to post
Share on other sites

New requests are now working fine for us. Unfortunately it appears I have to restart the last step for all affected requests (minimum 100). 

 

 

Link to post
Share on other sites

@BenKeeley

It would seem that you are one quite an old revision of the SM application,  we will need to create a specific hot fix for it, or with your permission we will update your SM version? You ok for us to do that?

Gerry 

 

Link to post
Share on other sites
5 minutes ago, Keith said:

New requests are now working fine for us. Unfortunately it appears I have to restart the last step for all affected requests (minimum 100). 

I can only apologise for this, if you need us to do this I am sure I can arrange this?

Gerry

Link to post
Share on other sites
9 minutes ago, Paul Alexander said:

@BenKeeley

Have you restarted the affected tickets (by pressing the 'retry icon next to the HUD)?

I think you need to have the admin role to see this though? I'm sure you have...but it's always worth asking!

image.thumb.png.9af79a1ebbedb4ae5f251a31f0f717e3.png

 

In my case, for these requests i am still having issues with, there is no restart icon on the right (i've used it in the past though). I am trying to manually assign a ticket to a team and it just throws up that error.

UPDATE: It's still affecting us for new requests or trying to assign manually.

Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...