Lewnatick Posted December 31, 2014 Posted December 31, 2014 Just a quick update for the other users in this thread: I spent some time in a shared session this morning with Pulseway support. They gathered a lot of information, and are doing some internal testing to try and reproduce this issue. Once more is understood about this issue, and more headway is made, I will update here.
Lewnatick Posted January 14, 2015 Posted January 14, 2015 The support team is still trying to figure out this issue. Nothing new to report.
Staff Chris Posted January 20, 2015 Staff Posted January 20, 2015 Hey everyone, Lewnatick worked with us and we've identified the issue. If there is anyone that still has the problem please contact support [at] pulseway [dot] com. Regards, Chris Pulseway Team Lewnatick 1
Lewnatick Posted January 20, 2015 Posted January 20, 2015 Hey everyone, Lewnatick worked with us and we've identified the issue. If there is anyone that still has the problem please contact support [at] pulseway [dot] com. Regards, Chris Pulseway Team I can vouch for what Chris said above. The support team did indeed get things working again, and I greatly appreciate their help. Chris 1
bbb Posted January 23, 2015 Author Posted January 23, 2015 Many thanks Lewnatick and Chris - been running the fix for a couple of days and it's back to normal. Appreciate both your efforts. Chris 1
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now