They're redundant headers as far as I'm concerned. It doesn't mean that any additional filtering is being applied to your account by the mx.lasts/mx.cores. I'll see about getting them removed.
They've only just started appearing. I may be wrong and haven't time to have a good old look back but I don't think I've EVER seen them before.
... I think you've been scathing enough already. We don't plan for problems to happen you know?
I have been scathing simply because PN keep repeating the same old fundamental mistakes over and over and over again. I keep seeing the apologies. I keep hearing that things have changed and it wont happen again in the future. I keep hearing that things are
always reviewed and tested. I hear ALL of the placating words that come out at times such as this but I'm very sorry, I also see very little substance in them after hearing them so frequently and for so long.
Customers still see fundamental and very obvious problems like this suddenly appearing. Things that have worked quite correctly for ages suddenly stop working simply because someone didn't bother to test their latest tweaks out effectively (if at all) before implementing them on the customer facing system. Someone presumably didn't even bother to monitor the system after the changes to find out if things were working as they should be either or you would have known about the issue and would have reported the issue before I (and presumably others) found it. It always seems to be the customers that do the testing and evaluation and not PN even when it could and should be so simple to avoid most of the silly mistakes that inevitably tend to happen when any changes are being made.
No service status either it would appear. Everything's all green and hunky-dory according to everywhere I've just looked. How can this be if PN already know there is a fundamental problem and are looking into it ? Is it any surprise that people get upset ? No, I think not.
I have no problem whatsoever with accepting that things sometimes go wrong no matter how hard you try to avoid it and no matter what the circumstances may be. I can totally accept the loss of 700GB of data due the rather unfortunate use of a fat finger in an inappropriate place but silly, totally obvious and totally avoidable fundamental issues like this are absolutely NOT in that category. This issue would have shown up had the changes been reviewed and tested prior to unloading them onto customers. PN may well believe that they do not plan for problems but they sure do make a real good effort to encourage them happening by apparently not taking even the smallest of steps to avoid them and mitigate the risk.
Specification.Specification.Specification.Specification.Specification.
Planning.Planning.Planning.Planning.Planning.
Management.Management.Management.Management.Management.
Review.Review.Review.Review.Review.
Testing.Testing.Testing.Testing.Testing.
The fundamental steps used by just about everyone involved in design/development who is NOT involved in anything PC, generic software or ISP related to maximise performance, minimise final costs, ensure quality and minimise avoidable problems from reaching customers and therefore causing annoyance, embarrassment or whatever. Not a 100% solution to any/all problems by any stretch of the imagination of course but a whole lot better than not doing it. Testing and Quality Control are intended to be in-house functions and not something that is generally sub-contracted to customers aren't they !
Sorry Bob, excessively scathing it might well be but I see yet another example of totally avoidable problems being totally encouraged to happen rather than learning from any/all past mistakes.