Adam Driscoll

@insomniaccWhat is your Api__SecurityModel setting set to? I ask because I'm not sure if this is related to the proxy and may be a different issue. 

@Matthew MorrowI opened an issue for this. We should be able to support that. 

@MarcoSure! We should be able to provide a range selector for this. 

@Matthew Morrow As I mentioned in our call, this seems buggy to me. We should already have a rolling session timeout. Any interaction should extend the timeout but that doesn't seem to be happening. I've opened an issue for it. 

@Dynamic66 Can you reproduce this pretty easily? If so, next time you see it, please press F12 and see if we have a network error regarding loading the chunk. I want to know if it's a 404 or something else. I've seen this before when there were caching problems, but this seems different. 

@Adam Driscoll Thanks for the info. Let me open a bug and do some digging. 

@insomniacc I'm not seeing that issue in my environment. We might need to dig in a bit. I would recommend checking the %ProgramData%\PowerShellUniversal\Logs folder for agents logs corresponding to the PS5.1 jobs to see if there is an error message we may be able to look at.

@Matthew Morrow Good idea. I think restarting APIs and environments would be good too.

@rmcavoy I've opened a feature in the backlog. I think we may be moving away from these guys in general so either there will be an option or they will disappear on their own.

@markusburkhardt Thanks for letting us know. I'll reopen this and have a look. I do wonder if it has to do with the fact this is in the modules view and not the Source Control \ Files view.

@Matthew Morrow That's a good idea. We do display them in the support tools but that's about it. It would be nice to do some management, and I like the idea of seeing how they different per environment. It will mostly be the PSModulePath there.

@rmcavoy Thanks for opening this! This one has been in our backlog forever. I checked, and it was first opened in 2020! I've selected it for development, and I'll see if we can get it into our next release.

@Matthew Morrow This is slated for 2027.1.0

@Matthew Morrow We certainly should have this. I've opened a feature request and will update this thread once it's implemented!

@fabiomatt Thanks for the suggestion! I agree this could be better. I've opened an issue in our backlog to get this improved.

@Dynamic66 We have a fix coming for this in 2026.3.4 -> 2026.3.3 - Error when attempting to connect to Terminals - Devolutions Forum

@jol Thanks. This makes sense. We do have the ability to ship modules to agents via environments. If you configure an environment and then set the Modules to Import, select Virtual and then run that script on an agent in that environment, the modules will be sent down to the agent that are listed.

We currently do not have a way to send modules configured for just a single script.

@Matthew Morrow Yep. We can fix this. It should match the other tables in the admin console anyways.

@dylk9 This is a good idea! Would you expect the usage of an expired secret to throw an exception?

For example, using something like this in a script, app or API would result in the access to throw an exception that the secret is expired. It may be clearer than an error returned by the target system.

$Secret:MyExpiredSecret

Our next community call will be Wednesday, November 18th, 2026, at 11am central US. We will continue to host these on the third Wednesday of the month.

These calls are hosted on our Discord server. https://discord.gg/Sb5ngcjkj4

Agenda TBD

This feature request was discussed during our October 2026 Community Call.

We technically support this and you can switch the entire repository, but we can't do individual folders.

The stated goal is that the user would like to have a git repo per app or module. When working in that app or module, you can commit to a different git repository than the other apps or modules. Each app folder would then be its own git repository but the root repository would not be.

This feature request was discussed during our October 2026 Community Call.

The current, online docs change over time and are typically scoped to the most recent version. There is no way to look up docs from previous versions.

We could either consider shipping the docs in the product (they are just markdown files) or figure out some way to update Gitbook to have a version drop down.

This feature request was discussed during our October 2026 Community Call.

A user request some way to share snippets with other users and display them in the portal. Snippets would include a PowerShell command and some markdown docs. Then users could quickly grab and run those snippets in PSU or in their local terminal.

I also think it would be nice to allow users to add their own snippets to store them in PSU for use later.

We could also consider making it a bit fancier and expose something like Jupyter notebooks where markdown and code are in the same document.

This feature request was discussed during our October 2026 Community Call.

Users have suggested that the dark theme in the admin console is too blue. We could either adjust the theme (which tends to match other Devolutions products) or have a theme picker to expand beyond just light and dark. If we had a simple set of tokens, we may even allow customizing the colors.

This feature request was discussed during our October 2026 Community Call.

A scheduling visualizer should be able to show upcoming scheduled jobs on a timeline view. This is primarily so that users can see overlapping schedules. We could have options to group by things like computer or computer groups as well as scripts or tags.

Another idea was to have a job history view that is similar but displays jobs over time, including the duration on the timeline.