Limit Mails not sent

[dudemanguyy]

Describe the bug
Timetracker does not send Emails in case a user is over time:
Failed to send limit email to user: Unable to build URLs outside an active request without 'SERVER_NAME' configured. Also configure 'APPLICATION_ROOT' and 'PREFERRED_URL_SCHEME' as needed. [in /app/app/utils/scheduled_tasks.py:1299]

To Reproduce
Steps to reproduce the behavior: User goes over 9h on workday time

Expected behavior
Email is sent to the user which has overtime for the day

Environment

• TimeTracker version: 5.11.4
• Deployment: Docker
• OS: Ubuntu 24.04

Additional context
Add any other context about the problem here (logs, config, etc.).

[evilguy4000]

@dudemanguyy
Thanks for the clear report and log line — that helped pin this down quickly.

Cause: Working-time limit emails (and other scheduled notifications) run in a background job with no HTTP request. Building the “justify overtime” link used url_for(..., _external=True), which needs either a live request or Flask SERVER_NAME. We don’t set SERVER_NAME (it can break reverse-proxy setups), so the send failed with the error you saw before the mail went out.

Fix: Absolute links in scheduled jobs now use a public base URL via APP_BASE_URL, with auto-detect from real browser requests as a fallback. This is included in 5.11.5.

What to do:

Upgrade to 5.11.5 (or later).
Preferably set in .env / Compose:
APP_BASE_URL=https://your-public-hostname.example
Use the URL users open in the browser (scheme + host, no path).
After that, going over the daily limit again should deliver the email with a working justification link. If it still fails, check the app logs around the limit job and confirm mail is configured (Admin → email / MAIL_*).

[dudemanguyy]

Works now. Thank you!