> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/mailscheduler/support/faq.md).

# 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>My performance progressively gets slower while using MailScheduler with Tableau Server, how can I fix this?</strong></summary>

When using Tableau Server (Tableau Cloud is unimpacted), make sure to have Viz data services enabled to massively increase the performance of MailScheduler exports. Below, you can see what happens over time when the Viz data service is disabled, vs the constant performance when it is enabled.

<figure><img src="/files/oUlz1dqgZ7m1jwLl8Cst" alt=""><figcaption><p>Tableau server without Viz data services enabled</p></figcaption></figure>

<figure><img src="/files/uFz5eglADkfqLGA4zomi" alt=""><figcaption><p>Tableau server with Viz data services enabled</p></figcaption></figure>

To enable Viz data service, you can use the following commands for the Tableau server:

```
tsm configuration get -k features.VizDataServiceClientEnable
tsm configuration get -k features.VizDataServiceBackgrounderEnable
tsm configuration get -k features.VizDataServiceHTTPEndpointEnable
tsm configuration set -k features.VizDataServiceClientEnable -v false
tsm configuration set -k features.VizDataServiceBackgrounderEnable -v false
tsm configuration set -k features.VizDataServiceHTTPEndpointEnable -v false
tsm configuration set -k features.VizDataServiceClientEnable -v true
tsm configuration set -k features.VizDataServiceBackgrounderEnable -v true
tsm configuration set -k features.VizDataServiceHTTPEndpointEnable -v true
```

</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="/files/MVETOCMhO56Uv8XjolXz" 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>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.infotopics.com/mailscheduler/support/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.