Administrators Darren Schreiber Posted June 2, 2017 Administrators Report Posted June 2, 2017 Sorry, no, code was committed this morning but we don't roll this during the day, we'll roll the fix tonight. I'll put a notice on the status page.
Karl Stallknecht Posted June 2, 2017 Report Posted June 2, 2017 Oh gotcha, thanks! Sorry I assumed committed meant it went live...used to dealing with routers :-)
Rick Guyton Posted June 5, 2017 Report Posted June 5, 2017 Seriously Tuly, thanks for spearheading this. Sounds like it's good now. If you are ever in the PHX valley, hit me up and I'll get you that beer. Thanks again!
Karl Stallknecht Posted June 10, 2017 Report Posted June 10, 2017 Has anyone else had more problems with this today? We received one report today that a call went back onto park automatically, although it's from a brand new client and we aren't confident that it wasn't just an error on their end since they just started using the system. Often times our new clients report weird behavior in the first couple of weeks and it's just from their own mistakes as they learn the new system, so I'm not sure if we should be concerned or not...?
Administrators Darren Schreiber Posted July 7, 2017 Administrators Report Posted July 7, 2017 I believe all these scenarios are now resolved, and there was also an issue where, in the process of attempting to fix the items you all were reporting, the "ring back" from a parked slot no longer had the parking slot number in the Caller ID. That's also resolved. Let us know if you're still having issues here.
Recommended Posts