dynamics in prod drop modules

when i am in dev everything loads fine, when i am in prod the dynamics will randomly unload my module and thus the cmdlet cannot be found, restarting the app doesnt help. if i load a new session in another browser it will work a little bit.

@mmorrow

Thank you for reporting this. The fact that the App works normally in development, but in production the cmdlet eventually becomes unavailable while a new browser session temporarily works, gives us a useful starting point.

To narrow down whether the behavior follows the browser session, the App runspace, or module availability in the production environment, could you please provide:

* The exact PowerShell Universal version and build running in both development and production.
* The module name and cmdlet that becomes unavailable.
* How that module is loaded in the App, for example through the PSU Environment module configuration, a Startup Script, or `Import-Module` in the App code.
* The exact error shown when the cmdlet can no longer be found.
* Whether development and production use the same PSU Environment configuration.

If possible, when the issue occurs, please also compare the sanitized output of the following between a working session and an affected session:

Get-Module <ModuleName>
Get-Module <ModuleName> -ListAvailable
Get-Command <CmdletName> -All
$env:PSModulePath

This should help us determine where the module availability is changing before making any changes to the production environment.

If you need to share PSU logs containing information that should not be posted publicly, you can send them directly to
ruben.tapia@ironmansoftware.com

Best regards,
Ruben Tapia