2026.2.5 - auto reload not working

Hello @Matthew Morrow

Thank you for reporting this.

From your description, the file detector appears to be noticing the change, but PSU is not automatically applying it and you still need to manually use options such as Reload Endpoints.

We will reproduce this behavior in our lab using PSU 2026.2.5 so we can properly document the results and prepare the case for internal escalation if the behavior is confirmed.

To make sure our test matches your scenario as closely as possible, could you please confirm:

• Is Auto-reload enabled under Settings > Files > Configuration Changes?
• Are you modifying the PSU files directly on disk, through VS Code, or by another method?
• Besides endpoints, have you noticed the same behavior with any other PSU resources?
• What hosting method and operating system are you using?

We are also working through the different reports you have shared, so we appreciate your patience while we validate each behavior individually and make sure the appropriate evidence is collected before moving them forward.

Because this is a public forum, please sanitize all evidence before posting. Remove credentials, tokens, license keys, cookies, private keys, full connection strings, email addresses, usernames, customer data, tenant or account identifiers, internal domains, hostnames, IP addresses, and private URLs. Please do not upload unredacted HAR files, memory dumps, database backups, or complete configuration files to this public thread.

Best regards,
Ruben Tapia

i will capture that next time it happens

also experienced it in 2026.3.2.0

dev environment
vscode
edit endpoint
go to site and endpoint doesnt know about the new code
auto reload enabled

shows the change resolved in /changes
new code does not show up in the editor
git editing button is = true
i have to go to reload config files to get it to see the changes

Hello @Matthew Morrow

We completed the lab testing for this behavior using PSU 2026.2.5 in Docker.

We were able to partially reproduce the issue. With Auto reload enabled, multiple external configuration changes were detected at the file level but were not automatically applied to the running endpoint. The behavior was repeatable across the final three test iterations.

We also confirmed that manually using Reload Configuration Files applied the latest change successfully, and the runtime consistently returned the updated endpoint version afterward.

One difference remains between our lab and your report: we did not reproduce the Configuration Changes history or the “Resolved” state you described, so we are keeping the result classified as partially reproduced rather than treating it as an exact match.

At this point, we have enough technical evidence to move the case forward for internal escalation and further review.

For now, the manual reload remains the validated workaround for applying the configuration changes.

Thank you again for your patience while we worked through the reproduction.

Best regards,
Ruben Tapia