This was the error I just received on the PE Website.
Sorry to say; something bad has happened.
Don't worry! Somewhere, a highly-trained engineer has been woken from his or her nap by their smartphone buzzing, informing them of all of the details of this particular little glitch.
We'll make sure they get it fixed before they get back to naptime.
All joking aside, to make this a constructive post, I was attempting to look at the monthly statements for my account. I got a nice chuckle though!
Nice Touch, Keith
-
- Posts: 9943
- Joined: Sat Oct 09, 2010 8:38 pm
- Location: Pompton Plains, NJ
- Contact:
Re: Nice Touch, Keith
That is all Tim right there, but thank you. hopefully he will have a diagnosis on the statement issue.
-
- Posts: 503
- Joined: Mon Jan 24, 2011 11:41 am
- Location: KPDX
- Contact:
Re: Nice Touch, Keith
Glad you liked it, Walt
I got the notice shortly after you ran into the issue. I'm in back-to-back meetings for the rest of the day but I'll try and get some time to look into it tonight and will advise when it's fixed up. In the meantime, if you need copies of any of your statements, just email billing@pilotedge.net with the details of what you need and I can turn those around for ya. Tim

Re: Nice Touch, Keith
No need, Tim. Was just looking to compare hours over the last few months. Thanks!
-
- Posts: 503
- Joined: Mon Jan 24, 2011 11:41 am
- Location: KPDX
- Contact:
Re: Nice Touch, Keith
Walt,
Try it again and see if you can see your statements now (note that the page unfortunately takes a little bit to load). The issue was actually with our billing provider's end - we were running on a slightly outdated version of their integration library and they had already addressed and fixed this issue upstream of us, so I brought us up to date. Looks to be good to go now.
Thanks for following up. Tim
Try it again and see if you can see your statements now (note that the page unfortunately takes a little bit to load). The issue was actually with our billing provider's end - we were running on a slightly outdated version of their integration library and they had already addressed and fixed this issue upstream of us, so I brought us up to date. Looks to be good to go now.
Thanks for following up. Tim