Known Issues

Here are all the known issues with OttoFMS.

Name	Status	Description
Pulling files over 1GB in size From windows is slow	in progress	The 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.
deployments aborted while a jit build runs will not delete the jit build	backlog	If 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 happens	backlog	If 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 confirmations	backlog	Some webhook providers require a confirmation step before you can send webhooks. The OttoFMS webhook setup has no way to handle this easily.