Include automation after customer changes Requires Recrawl Settings

[danielabloch]

Is your feature request related to a problem?

When a WP customer makes changes to their plugin settings (under Requires Recrawl Settings), they have to message Parse.ly support to let them know of the change, so that they recrawl the site.

Describe the solution you'd like

Ideas to consider:

• If someone makes changes here, automatically send an email to support and cc the VIP user, so the request to reprocess the data doesn’t rely on the customer,
• If someone makes changes here, automatically initiate a recrawl on behalf of the customer.

[acicovic]

@arhine, @thompsonjoshua, do you think it would it make Parse.ly support a service to send an automated "Recrawl settings updated" email, citing the domain name that has been updated? We would send the email and notify the user that Parse.ly support has been notified of the event.

[thompsonjoshua]

I like the idea of streamlining the process but I'm also thinking of some edge cases that could happen:

• a customer modifying their settings in the first few days of integration won't need a recrawl
• a customer that makes multiple changes and saves in a row would generate multiple emails that would Round Robin to different support members
• the recrawl process isn't ready for automation:
  • we run recrawls on posts and non-posts separately
  • we try to limit ourselves to recrawling <100k posts at a time to minimize timeout errors.

If a customer does want a recrawl, they might actually want a rebuild too. If we do a recrawl without a rebuild, they might not understand the results, i.e., split posts from different eras of metadata. Also, customers oftentimes don't have any concept of the labor or machine costs of recrawls and rebuilds (and why should they?) so they might go about requesting several in a row.

My preference is to de-prioritize this item in favor of other plugin pursuits.

[acicovic]

@thompsonjoshua, thank you for your input!

[acicovic]

Given the feedback, I'm suggesting to close this issue.