Known Issues

Known Issues

Here are all the known issues with OttoFMS.

NameStatusDescription
OttoFMS unstable on Soliant serversclient reviewSoliant-hosted servers are experiencing infrastructure-related issues that impact the operation of OttoFMS. We’re actively working on solutions to enable Soliant servers to run OttoFMS smoothly. If your server needs immediate attention, please note that Soliant is aware of these challenges and is currently the only party capable of resolving them.
Pulling files over 1GB in size From windows is slowin progressThe web server on Windows, IIS, throttles large file requests aggressively. On our latest test, a 30GB file takes 4 hours to get pulled from a Windows source server. This affects deployments that use either install or replace as the file options and a Windows Source server. We are testing solutions for this problem. Migration deployments are unaffected.See "handling large files" in the docs for how to work around these issues.
Filenames containing non-Unicode characters cannot be deployed on WindowsbacklogThe fmsadmin tool on windows is not returning Unicode characters in its output to OttoFMS, causing deployments of these files to fail.
deployments aborted while a jit build runs will not delete the jit buildbacklogIf a deployment is aborted while a just in time build is still running, the build will not be deleted from the source server as expected. This build will be deleted later with a different process (either the max builds to keep in outbox setting or when OttoFMS restarts).
jit build does not get deleted when timeout happensbacklogIf a Just in Time build times out after 30 minutes, the build does not get deleted from the source server.
Webhook Receiver doesn't have a way to do confirmationsbacklogSome webhook providers require a confirmation step before you can send webhooks. OttoFMS webhooks do not support this natively, although it can be set up using Webhook Responses. Check out the Webhooks docs for more information.