Branching a master module to dev sometimes fails. From the logs it seems to be an issue related to improper directory path generation and thus an incorrect path is passed to the system script handling file movement.

App cannot connect to another engine by only logging out. The Devin app has to be re-started.

The session count and file size does not automatically get refreshed. Clicking "Reload" refreshes it correctly.

In some cases, the app might fail to login on first attempt after app install/update. Re-starting the app or FileMaker Pro should resolve the issue.

The Devin Engine version might show as “engine version error” in the app and other places. This does not affect any features.

If auto-deploy is enabled AFTER a module has been released, but before files have been triggered for migration, the minimum inactivity period setting may not work as expected.