# FAQ

<details>

<summary><strong>Does Apps for Tableau look at any of my data?</strong></summary>

No, MailScheduler is a on-premises solution without the need of any internet connection. Our SaaS solutions are hosted in an isolated Azure environment only accessible for a by you approved group of engineers.

</details>

<details>

<summary><strong>Can MailScheduler run in docker  / kubernetes?</strong></summary>

Yes MailScheduler can run in a container. The configuration for this is next-level since it needs to be configured manually without the one-click installer.  Reach out to our support channel for the possibilities.

</details>

<details>

<summary><strong>Can I change the API version of the Tableau Rest API that MailScheduler uses?</strong></summary>

Yes, you can change the version of the Tableau Rest API that MailScheduler uses. The default is 3.15. You can change this version in the general settings.

</details>

<details>

<summary><strong>How to set the number of parallel requests to the Tableau Rest API?</strong></summary>

You can change this number in the general settings. Please keep the concurrency limits in mind.

</details>

<details>

<summary><strong>Can you explain more about the config toml file structure?</strong></summary>

The config toml is a configuration file located in the installation folder. Here we store some variables and secrets. Note that it is wise to limit access to the installation folder or server to keep your secrets secure.

Once you open the file you will see the contents.&#x20;

```yaml
[mail-scheduler]
domain = 'localhost'
host = '0.0.0.0:8080'

[mail-scheduler.env]
app_license = ''
app_url = 'http://localhost:8080'
db_connection = 'sqlite-default'
db_database = 'mailscheduler.sqlite'
db_driver = 'sqlite'
db_host = ''
db_password = ''
db_port = ''
db_schema = 'public'
db_username = ''
encryption_key = ''
encryption_salt = ''
user_created = true

[mail-scheduler.proxy]
enabled = false
external_domain = ''
external_port = 0
external_ssl = true   
```

**IMPORTANT:** After saving any changes to the config.toml, you will **always** need to shut down and restart the Mailscheduler app, or they will not be applied properly.

</details>

<details>

<summary><strong>Can I change the PDF caching time</strong></summary>

This setting can be changed in the general settings.

</details>

<details>

<summary><strong>How does MailScheduler handle timezones for scheduled messages?</strong></summary>

The time you set in the schedule (e.g., **07:00**) is based on the timezone configured in your MailScheduler settings.

**To change the timezone, you can change this value in the general settings.**

<figure><img src="https://1937398298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOEnvavVjEKojggGVc69T%2Fuploads%2FKKuuzg8uksdzuGDhPas2%2Fimage.png?alt=media&#x26;token=04857973-2658-4da6-a720-e387abe071ab" alt=""><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Does the application provide a health check endpoint for load balancers?</strong></summary>

Yes. Our application exposes a dedicated health check URL that load balancers can call to verify that the application is running and ready to accept traffic. The Url is the http\://\[hostname]/health or https\://\[hostname]/health when you are using ssl

</details>

<details>

<summary><strong>Why can’t I access the MailScheduler from the internet?</strong></summary>

The MailScheduler runs only on the local virtual machine (VM) and is **not hosted on a public server**. Because the VM has no public IP address, it cannot be accessed from the internet.

To make it work inside the VM:

1. Open the `hosts` file (`C:\Windows\System32\drivers\etc\hosts`).
2. Add entries that map loopback addresses to your domain, for example:

This ensures the MailScheduler runs correctly and can send emails from the VM.

```
127.0.0.1 mailscheduler.yourdomain.com
127.0.0.2 mailschedulernew.yourdomain.com
```

</details>