Some customers may encounter issues with the delivery of auto-generated reports via email. A common symptom of this problem is that reports appear to be generated correctly but are never actually sent out. This can be especially frustrating when email delivery is a critical part of your team's workflow.
A Possible Root Cause: Email Server Timeout
In many cases, the underlying cause is a timeout when connecting to the email server. By default, the system waits up to 10 seconds (10,000 milliseconds) when attempting to connect to the configured email server. If the server is slow to respond - due to network latency, load, or other factors - the connection attempt may fail before it's established, and as a result, the email never gets sent.
The Solution: Customize the Timeout
To address this, we provide a configurable environment variable:
REPORT_SENDER_TIMEOUT_MS
This environment variable lets you increase the timeout duration to better match your infrastructure needs. For example, if your mail server occasionally takes longer than 10 seconds to respond, you might want to set:
REPORT_SENDER_TIMEOUT_MS=30000
This increases the timeout to 30 seconds, giving your application more time to establish the connection before aborting the attempt.
Default Value
If this variable is not explicitly set, the system will default to:
REPORT_SENDER_TIMEOUT_MS=10000
That’s 10 seconds, which is sufficient in most cases, but not all.
When to Adjust This Setting
You should consider increasing the timeout if:
-
Your email reports are not being delivered even though everything else seems correctly configured.
-
You notice delays or timeouts when testing the email connection.
-
You're using a third-party mail provider that may be rate-limiting or experiencing temporary slowdowns.
Pro Tip: Test the Connection
After adjusting the environment variable, it's a good idea to test the configuration by triggering a report manually to ensure the connection completes successfully.