Troubleshooting Versioned Applications

This page covers common issues Creators encounter when working with versioned applications and how to resolve them.

Branch Pill Is Not Visible

Issue: The branch pill does not display in the module toolbar when editing a module.

Cause: Application versioning is not enabled on the application.

Resolution: Enable versioning from the application settings. In the Explorer panel, select Settings from the application's ellipsis menu, find the Versioning section, and click Enable versioning. Note that enabling versioning is permanent and cannot be undone. See Application Versioning for details.

"Create Branch to Edit" Message Displays

Issue: The module toolbar displays "Create branch to edit" and the Save button is disabled.

Cause: The active context is a published version or the default version, both of which are read-only.

Resolution: Create a branch from the current version to begin editing. Open the Manage Versions dialog from the checkout pill, then select Create Branch from [version] from the version's ellipsis menu. See Creating Branches.

Publish Blocked by Draft Dependencies

Issue: The Publish dialog displays a "Draft dependencies must be resolved" warning and the Publish button is unavailable.

Cause: One or more of the application's dependencies reference a draft (unpublished) version of another application.

Resolution: Open the Manage Dependencies dialog from the checkout pill and update each flagged dependency to reference a published version. Return to the Publish dialog after all dependencies are resolved. See Application Dependencies.

Stale Base Warning When Publishing

Issue: The Publish dialog displays a warning: "Branch isn't based on the current default."

Cause: The branch was created from an older version. The current default version has changes the branch does not include.

Resolution: This warning is informational and does not block publishing. Use the Compare with active version button in the warning to review the differences. If the differences are acceptable, proceed with publishing. If not, merge the current default into the branch first. See Publishing Branches.

Revert to Button Is Not Visible

Issue: The Revert to button does not display on commit rows in the Branch History dialog.

Cause: The Creator viewing the history does not have update permission on the application.

Resolution: Contact a workspace administrator to grant update permission on the application. See Branch History.

Manage Dependencies Is Not Visible

Issue: The Manage Dependencies option does not appear in the checkout pill.

Cause: The application does not have versioning enabled, or the Creator does not have update permission on the application.

Resolution: Confirm versioning is enabled on the application. If it is, contact a workspace administrator to grant update permission. See Application Dependencies.

Merge Conflicts Not Resolving

Issue: The Merge button in the merge bar remains disabled after making resolution choices.

Cause: One or more modules still have unresolved conflicts. The progress bar in the Summary Bar displays the remaining count.

Resolution: Use the Conflicts scope tab to filter the module stack to only unresolved modules. Work through each module and select a value for every conflicting row. The Merge button in the merge bar becomes enabled when all conflicts are resolved. See Merging Branches.