OEMobile performance issues in development

Posted by John Goodland on 08-Nov-2013 04:34

Anyone else having issues using OEMobile to the point its unusable? Frequently getting the "Down for maintenance message appearing"

All Replies

Posted by John Goodland on 08-Nov-2013 06:54

strange one, but its all up and running now..... maybe those PUG people in Brussels had a workshop ;)

Posted by John Goodland on 08-Nov-2013 08:33

spoke to soon - - down again.....

Posted by John Goodland on 08-Nov-2013 08:40

"We are currently down for maintenance."

Translated to "Its Friday afternoon in the UK time to go home"

Posted by Ankur Goyal on 08-Nov-2013 12:25

Checking on this John. I know this wasn't scheduled.

Posted by jackiep on 11-Nov-2013 08:07

It's just happened to me.  That's two working afternoons in a row now (Friday and today).

Posted by jackiep on 11-Nov-2013 09:19

... Back again, just a brief down this time.

Posted by John Goodland on 12-Nov-2013 03:09

generate IPA file after 10mins returns

"We are currently down for maintenance."

Arrrrrrrrrrrrrgggggg please can someone at Progress resolve this ? and yes I do have a call open since Friday with no answers as to why this is happening

Posted by John Goodland on 12-Nov-2013 05:10

now I cant access project.mobile.progress.com

Posted by Fabrice Leste on 12-Nov-2013 10:45

Fyi, it should be working fine now. Sorry for the inconvenience.

--Fabrice

Posted by Peter Mellow on 12-Nov-2013 15:26

Our vendor is looking into why the mechanism they have in place for detecting this situation, failed to provide the heads up on the problem. We are actively chasing after them for answers on that.

Peter

Posted by John Goodland on 13-Nov-2013 02:51

Thanks Fabrice/Peter and team - everything is happy again in OEMobile world.

Although things have been frustrating for us (and others) over the last few days I understand Cloud development is new (for most of us) and expect a hiccup or two along the journey. The recent outage/performance problems has highlighted some failure in the alerting, which I'm confident Progress will put procedures in place to ensure it won’t happen again.

This thread is closed