# \[Bug\] Report paths for gateways on non-windows systems produce badly behaved paths

**URL:** <https://forum.inductiveautomation.com/t/bug-report-paths-for-gateways-on-non-windows-systems-produce-badly-behaved-paths/116656>\
**Category:** Ignition\
**Tags:** vision, ignition83, perspective\
**Created:** [August 4, 2026, 6:04pm UTC](https://forum.inductiveautomation.com/t/bug-report-paths-for-gateways-on-non-windows-systems-produce-badly-behaved-paths/116656 "2026-08-04T18:04:27Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mmyzer](https://avatars.discourse-cdn.com/v4/letter/m/87869e/32.png) [@mmyzer](https://forum.inductiveautomation.com/u/mmyzer)\
**Post date:** [August 4, 2026, 6:04pm UTC](https://forum.inductiveautomation.com/t/bug-report-paths-for-gateways-on-non-windows-systems-produce-badly-behaved-paths/116656/1 "2026-08-04T18:04:27Z")

</div>

## Setup

> **Version Info**
>
> | Module | Version | License |
> | --- | --- | --- |
> | Ignition Platform | 8.3.8 (b2026071409) | |
> | SFC Module | 6.3.8 (b2026071409) | Trial |
> | Event Streams Module | 1.3.8 (b2026071409) | Trial |
> | Perspective Module | 3.3.8 (b2026071409) | Trial |
> | Reporting Module | 7.3.8 (b2026071409) | Trial |
> | Symbol Factory Module | 8.3.8 (b2026071409) | Trial |
> | Alarm Notification Module | 7.3.8 (b2026071409) | Trial |
> | OPC-UA Module | 10.3.8 (b2026071409) | Trial |
> | Enterprise Administration Module | 5.3.8 (b2026071409) | Trial |
> | Legacy DNP3 Driver Module | 5.3.8 (b2026071409) | Trial |
> | Historian Core Module | 1.3.8 (b2026071409) | Trial |
> | Vision Module | 12.3.8 (b2026071409) | Trial |
> | SQL Bridge Module | 11.3.8 (b2026071409) | Trial |
> | Kafka Connector Module | 1.3.8 (b2026071409) | Trial |
> | WebDev Module | 6.3.8 (b2026071409) | Trial |

I am running the Ignition gateway through a container (WSL2-based) on a Windows system. I am running Ignition Designer on Windows
## Steps to Reproduce

1. Open designer to a project
2. Create a new report
3. Under schedule, go to actions
4. Enter a valid Linux path. Examples below.

### Expected Behavior

Designer should accept the valid path.

### Actual behavior

Ignition throws an error:

```python
Attempted Action could not complete. WARN: Error in running distribution Save File for report ReportName-- Unable to write PDF to file '/usr/local/bin/ignition/my-example-path/file.pdf

```

### Additional examples

For simplicity, anytime the `%%` appears below, it is the `/usr/local/bin/ignition/` directory on the container system. In addition, I will try having the filename as `outputs/today/file.txt`.

| Folder Path | Result |
| --- | --- |
| `~/folder` | Fail, and `%%/~/folder` is created (yes, `~` is the name of the folder) |
| `folder` | Fail, but `%%/folder/outputs` is created |
| `C:/folder` | Success, output to `%%/F:/folder/outputs/file.txt`, there `F:` is the name of the folder. |
| `/home/ignition` | Success, output to `/home/ignition/folder/outputs/file.txt`, as expected. |

As shown, the behavior is wildly inconsistent. It can write to it's `%%` folder, but ONLY if it is using a "Windows path". Additionally, even on failures to save the file, the folder paths are still created, even if they use reserved characters.