Known Issues
Here are all the known issues with OttoFMS.
| Name | Status | Description |
|---|---|---|
| OttoFMS does not work unless using the full admin account | backlog | OttoFMS will not work if using external authentication or Local Directory accounts to log in. While these accounts work with the admin console, they do not work properly with the fmsadmin tool, which OttoFMS is using behind the scenes to run a significant portion of its functionality. Please ensure that you are logging in with the full admin account in OttoFMS. |
| offsite schedules with spaces in the name fail | backlog | if an offsite schedule has a space in the name it will not be recognized by OttoFMS and backups will not be sent offsite. |
| Filenames containing non-Unicode characters cannot be deployed on Windows | backlog | The 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 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. OttoFMS webhooks do not support this natively, although it can be set up using Webhook Responses. Check out the Webhooks docs for more information. |
All rights reserved.