I have a large v7 membership site that for some reason requires members to be saved twice before the member index will reflect the changes made to the member. This is a problem because, as an example, changing a member group from Paid to Suspended would still return the member in the member only search results because the member groups have not updated for the member in the search index.

There looks to be similar member indexing issues in v8 that are now fixed but that doesn't help in v7. Are there any known ways around this or a safe way to use the events system to trigger a second save event without ending up in a stackoverflow situation?