We have a large Connections deployment, with over 400,000 communities, many with over 100,000 members. The communitymembership task, if indexed daily takes 4.5+ hours. If we do it weekly, it can take over 16 hours to complete. The task only logs when it started, and when it finished, and nothing in between. In cases when it runs for longer periods, there is no way to tell what it is processing, or that it is still processing. Please consider enhancing the logging and, or tracing options for this task, to allow administrators to identify how much data has been processed, e.g. the number of communities processed, and their CommunityUuids. This would provide much needed visibility into this task.