Hi everyone,
I’ve been using Axigen to manage our team’s mail for a while now, but I’ve recently hit a persistent technical snag where the WebMail interface becomes sluggish and our local clients start throwing connection timeout errors.
I am currently using a ‘windows app’ community setup to handle some automated data logging and script execution on the same machine I use for my administrative tasks. I’ve noticed that whenever the background executor starts a high-intensity processing cycle, the Axigen WebMail interface begins to “hang” when I try to open or delete messages. Sometimes the list doesn’t populate at all, and I have to refresh the browser multiple times to see new arrivals. It feels like the background process is competing for the same CPU threads and memory that the browser (and the local mail services) need for real-time synchronization.
I have a few related technical questions for the sysadmins here:
I’m not sure if the way a windows app style environment manages its internal networking is causing a conflict with the AJAX or WebSocket connections used by the Axigen WebMail interface. Has anyone else encountered performance bottlenecks or “Socket Connection” errors in their logs while running high-level script executors in the background? I am also wondering if there is a way to prioritize the browser’s resource allocation or if I should look into adjusting the maximum number of concurrent connections in the Axigen processing settings to prevent these timeouts.
I really need to keep this automation active for my work, but the constant UI lag is making it very difficult to manage my inbox efficiently. If anyone has experience optimizing a professional setup for concurrent usage of heavy script executors and Axigen’s web tools, I’d love to hear your advice!
Thanks for the help!