Why are subscription change emails sent without activity log entries?

Related Scenarios

• Why do clients receive subscription change emails when no changes are made?
• How to prevent unnecessary subscription change notifications?
• What causes subscription change events without activity log entries?

Solution

When customers get emails about subscription changes but there’s nothing in the Activity logs, it usually happens because of API calls or hitting the Update Subscription button without really changing anything.

You can make changes to the Subscription and then undo them. This makes it look like nothing happened, meaning it will set off the event but won’t show up in the Activity Logs. These actions might lead to Subscription Changed events being recorded, causing emails to be sent out, even though there aren’t any real changes in the activity log.

To avoid getting such email notifications, follow these steps:

1. Review API Usage: Ensure your engineering team reviews the API calls made using the Retool API key.

   • Check if the Update Subscription button is being used without making changes.
   • Identify any unnecessary API calls that might trigger subscription change events.

2. Modify API Implementation: Adjust your API implementation to avoid triggering events when no changes are made.

   • Implement checks to confirm changes before making API calls.
   • Consider adding conditions to only send updates when there are actual changes to the subscription details.

3. Test Changes: After modifying the API implementation, test to ensure that subscription change emails are only sent when actual changes occur.

   • Monitor the activity logs to verify that only relevant changes are logged.
   • Ensure no unnecessary emails are sent during the testing phase.

Important Notes

• Ensure your API keys are securely managed and only used for intended purposes.
• Regularly audit your API usage to prevent similar issues in the future.
• Consider setting up alerts for unusual API activity to catch potential issues early.
• Collaborate with your engineering team to ensure best practices in API usage and email notification management.