Well I’m sorry to seem apathetic; I am actually reaching out to understand your pains and all. But you know, and we just have to admit, that there are MANY other battles to fight before we get to non-prod downtime. Like production downtime.
TBH, that’s what I do to my users, too.
But for the integration endpoint (ecommerce site, for example), my downtime is like 3 hours. The rest of the day/days is setting up other endpoints, ensuring reporting and task agent work, blocking access to some new feature (like part parameter editing in Time Phase), etc.
Which is a little messed up, that means they could turn off your pilot for a week for the fun of it. Pilot should have a SLA too, it should just be more lax than it is for live. Well, as its supposed to be for live.
It’s extra frustrating to have this effect an environment that was updated to 25.2.10 a week ago using the CMP. What’s the point of being able to update early if I’m still gonna get taken out by everyone else’s updates
We got the all-clear yesterday afternoon for our Flex Pilot upgrade to 2025.2.10.
Saw the extended maintenance announcement…just for spits and giggles I tried going to our Pilot site. First time the site it was a blank page with “test mode” on it…closed browser, tried again, now getting a 502 Bad Gateway nginx/1.23.2 message.
Happy Wednesday
Glad we didn’t tell all our users to start testing Pilot this morning.
Yep this is typical. No explanation why or a suggested time when it will be up and running. In the mean time our testing window is getting shorter and shorter. They also threw in maintenance update tonight so more time off of our testing window. Really frustrating!!!
I recognize this is several weeks old, but since we’re going through another upgrade this weekend I thought I’d drop in.
I’m pretty sure I received the Complete email this morning – yet, now even 30 minutes after, we’re still getting the 502 Bad Gateway nginx error on all our REST API calls.
Is that because they actually weren’t “Complete” or is that systemic issue related to overloading the gateway from all the retries and will settle?
