5.3. High availability

In a high-availability authoring environment, when one user imports a project, another user is unable to see it [RHPAM-2470]

Issue: When multiple users connect to a high-availability Business Central and one user creates a project, another user cannot see the project.

In a high-availability authoring environment, role changes in Business Central are not saved [RHPAM-2342]

Issue: If you configure a role change in high-availability Business Central, the change can be lost after a time and the roles reset to defaults.

In a high-availability authoring environment, an imported project in Business Central appears multiple times [RHPAM-2372]

Issue: If you import a sample project in high-availability Business Central, the project can appear in the list several times. Some copies might not have all of the assets. The environment can slow down when this issue occurs.

In a high-availability authoring environment, project creation fails when a Business Central node is down [RHPAM-2475]

Issue: When you create a project, the project creation does not complete. The cause is one Business Central node in a high-availability authoring environment going down.

In a high-availability authoring environment, asset creation is not completed when a Business Central node is down [RHPAM-2476]

Issue: When you create an asset, the asset is not indexed. It is displayed in Business Central but you cannot use it. The cause is one Business Central node in a high-availability authoring environment going down.

In a high-availability authoring environment, multi-project import slows down Business Central [RHPAM-2477]

Issue: When a user imports multiple projects in a high-availability Business Central with multi-project import enabled, Business Central slows down and consumes significant resources.