6 ms·
I can totally relate to that. In flood of notifications I missed information about expiring CC. Instead of somehow soft-locking the account they just downgraded
by aeonflux 7y ago
I can totally relate to that. In flood of notifications I missed information about expiring CC. Instead of somehow soft-locking the account they just downgraded it and all my integrations, hooks and god knows what just blowed. I managed to fix the CC in 5 minutes, but many months after I am still recovering from that disaster. Support replied that they did send warning so I should just FO.
- tyingq 7y agoThat's a terrible process. As you say, a "soft lock" of some kind is the obvious fix. They are basically encouraging you to jump ship because at that point, it's a similar effort to move to another vendor.
- en-us 7y agoIMO at that point since you have to rebuild everything anyway, just rebuild it with a different vendor. No reason to stay with a company that treats you like that.
- deleted 7y ago[deleted]
- scient 7y agoSo you are blaming them for your own fault?
- gnud 7y agoPretty sure he's blaming them for deleting all his configurations, not for disabling them once the CC bounced. And I agree. If that happened to me, I would move, without a doubt.
- hombre_fatal 7y agoThere are graceful, helpful ways to deal with accidents, and then there are awful, hostile ways. Ideally your service provider helps you through accidents. Both sides benefit from that.
- urbanjunkie 7y agoYou are an unpleasant little cunt, aren't you?
- 52-6F-62 7y agoOh that's odd. We've been running into CC issues on our team and we were "disabled". So we had no access to our production repos but AFAIK nothing was downgraded.