Segments are very slow! Any tips?

[WBJC915FM]

I'm a very unhappy user who's relied heavily on tags up until we went over 10k subscribers. Now I'm fighting with segments that are so extraordinarily slow to populate. 

I'm scheduling a series of 3 emails to go out a week apart from each other. One goes to List A today. The next goes to List B next week.  The third email goes to a larger list of 400, but not to those who are also members of List A or B.

This last one I've created a segment that is just perpetually populating for the last 20 minutes. I'm unable to complete the scheduling until it finishes!

I need to leave work, and I didn't realize it would take this long to get this done. Am I doing something wrong?

[Nick_S]

Hi @WBJC915FM,

I am sorry to hear the segments did not load quickly for you. I know it's the next day now, but did the segment ever populate? For matters like this, we would want to troubleshoot and see if there is a connectivity issue or something else that might be interfering with the site. For example, any chance you tried using another browser or incognito/safe mode to see if the process ran more smoothly? This is just for the purposes of seeing if it's actually the platform or the browser that is experiencing issues. If we can identify that it's the browser, we can investigate further to see what might be causing the stalled loading.

[WBJC915FM]

I've logged in this morning from a different computer and location and the segment is complete. I can try creating a different one and try different browsers. I'm usually always using Chrome on any of the 4 computers/2 locations.

I'll report back!

[Nick_S]

Hi @WBJC915FM,

I'm glad it completed! I'm wondering if maybe it had completed, but some kind of connectivity issue was preventing it from appearing completed on your screen (I'm just spit balling here). Definitely let me know if you have further issues, though!

[WBJC915FM]

Well I've created several other segments and refreshed others... none seem to take more than 5 minutes now. So that's good! I'll see if the issue persists at my other location. 

Whew!