Immediate Action Required: Recurring License Renewal Failure and Request for Permanent Resolution
Dear [Support Team / [Company Name] Licensing Department],
We are writing once again regarding the recurring license renewal issue that continues to disrupt our webhook-based mission-critical system.
Despite your previous assurance (in your message dated [23 days ago]) that our licenses would be manually renewed each month on the 27th without further intervention from us, the problem has reoccurred. This repeated failure is deeply disappointing and unacceptable, given the critical nature of our operations.
We request that you treat this matter with the highest priority and take the following actions immediately:
-
Immediate reactivation of our PRO license to restore full functionality without delay.
-
Permanent resolution — such as extending our license programmatically for one full year, since we are committed to continuous payment.
-
A written explanation clarifying why the previously promised automated renewal on the 27th failed again.
-
An official statement regarding compensation for the repeated service interruptions that have affected our operations over the past several months.
This issue was already addressed before, and the fact that it has resurfaced raises serious concerns about the reliability of your renewal system. We expect a clear, actionable response within 24 hours and assurance that this problem will not occur again in the future.
Thank you for your prompt attention to this urgent matter.
-
Hello 한국건강기술,
We apologize for the inconvenience. We manually fixed the bug for a few months in your account. Later, we had released a fix for this bug and we were hoping the issue will not recur. Unfortunately the bug continues. We will know if the patch is effective only based on user's subscription renewal experience and we have no way to confirm it ourselves. This bug is more challenging to fix due to the lack of immediate feedback about the effectiveness of the patch.
We have manually fixed it again in your account. We are continuing to work on developing a permanent fix for this bug. We will continue the manual fixing regime until we have a permanent fix.
0
Please sign in to leave a comment.
Comments
1 comment