Please Log in to join the conversation.
Yes, the plugin is to receive an update dividing Cancellation and Expiration into their own fields for separate query usage. Currently however unsubscribing, expiring, etc... in any fashion results in the Deactivation query executing. Please ensure you've properly built your query and have debug mode ON when performing tests for your query.Is the "on DEACTIVATION" the appropriate field for SQL Statement fored when Subscription expires??
Please Log in to join the conversation.