When you delete a recipe, EVERYTHING is deleted, including all trigger records in the system. Be very careful if you delete recipes, because there is simply no way to recover data associated with that recipe. (If a trigger is in more than one recipe, the recorded actions for the other recipe will still be retained; only records related to the recipe being deleted are affected.)

If the plugin was included in any triggers, the recipe can no longer be completed. Actions will never run. The recipe will remain intact but will effectively become locked. If the plugin was associated with actions, those actions will simply be skipped. There is no way to trigger them again later, so be very careful about deactivating and deleting plugins associated with active recipes.

Many batch operations in plugins skip the normal processes and Automator can’t recognize them. Anything that goes directly to the database, like user uploads, is an example of this. For some LMS plugins, bulk adding users to a course might also cause recipes tied to those behaviours to get skipped. There is unfortunately no way for us to change this behaviour; our Automator triggers rely on normal operations from the plugin integrations, which are sometimes skipped in batch operations.

Uncanny Automator can be GDPR compliant, but whether or not it is for you depends on what data you capture and how you use it. If you have recipes that capture form data that includes personally identifiable information then you are likely to run into GDPR challenges. Always make sure to only capture as much information as you need to create recipes and no more, and if you do capture personally identifiable information in your recipes, make sure you make your users aware of it.

Deleting triggers and actions live recipes is always risky and should be done with extreme caution. Triggers carry the most risk when multiple triggers are in a recipe. If a recipe has 2 triggers and some users have completed the first but not the second, if you delete the second trigger nothing will happen. The existing users that have trigger records will be stuck because there is no second trigger available to fire the recipe. In situations like this, you might consider replacing it with a second trigger that can easily be triggered by everyone, like a visit to the landing page where users arrive after they sign in. That will cause the recipe to fire for those historical users will ensuring other users are still excluded because of the first trigger.

The answer depends heavily on how you use Automator—if you have dozens of recipes, tens of thousands of users, and your recipes are very complex with many triggers and actions, then yes, there could be a marginal performance hit. Try to collect only as much data as you need; as an example, we discourage using the plugin as an analytics tool (e.g. setting up recipes to track all page visits across a site). For general use and in the vast majority of situations, you shouldn’t notice any performance impact while using Automator.

Absolutely! The plugin was created with translation in mind and tested with a variety of translation plugins. We will support translation issues if you run into any.

It does! Make sure you use our Business or Unlimited plan though so what we can offer support for your Multisite installs.

Absolutely! Your license can be upgraded at any time by paying the difference in cost between current license type and the new one. Please note that discounted upgrades are not prorated and do not extend the renewal date, so it’s best to upgrade shortly after the original purchase.

We will issue full refunds for any reason as long as the request is made within the first 14 days following your first purchase. Refunds will not be issued if the request is made more than 14 days after purchase or a refund for Uncanny Automator has previously been issued.