I'd be more than happy to help you out. 1. On the first rule, it sounds like you're using the correct event and have the action set up correctly, but you're having trouble with the condition portion of your rule. Event: Member profile is updatedCondition: Check array value ( You want to check the array of profile fields that have changed for the "pp_main_photo" key )Action: Create new topicrule-when-member-photo-is-updated.xml 2. What you want to do in a situation like this is to create a custom action which you will use to create the topic. You will then schedule this custom action to happen in 30 days. That custom action then becomes a new event in the system that you can attach additional rules to so that you can check conditions when that action is invoked at the scheduled time, and take additional actions at that time such as either creating the topic if the member has indeed been inactive for the 30 days prior, or if not, rescheduling the custom action to happen again in another week or so which will repeat the process indefinitely. As for the scheduling key portion of the equation, whenever you schedule an action, custom or not, you can enter a "scheduling key" for the action which will give it a unique identity so that you can operate on it later (such as delete it, or re-schedule it). When you use a scheduling key, you usually want to include a token of some sort from the event that will make it unique to a certain aspect of the event, such as the member id of the user it is being scheduled for. So the scheduling key for your use would look something like this: create inactive topic for member:[member:member_id]So when you schedule an action again with that same key, the old one is removed and only the new one remains (hence re-scheduling).