When verifying the application with MSC, there are a couple of common cases that may cause warnings or anomalies.

Check Orphan Methods

Orphan methods are typically caused by a deleted form where the method was not deleted along with the form. 4D keeps the orphan method just in case the user wants to reference back to it. However, the orphan method may reference to some resource not used anywhere and cause a verify warning. To resolve this issue, simply delete the orphan method

Problem on page # in B-tree Index

Typically caused by some data corruption (E.G. user disconnect while writing to a record). To resolve this issue, delete the .4DIndx and .4DIndy files to let 4D recreate the index files from scratch.

References to (someMethodOrFormObjectHere)

If there is a warning or error that is enclosed by the open and close parenthesis, that issue refers to a deleted item in the Trash. To resolve this issue, use the Explorer window > Trash tab to empty out the trash.