Checking for Consistency and Errors
Cogynt Authoring contains built-in mechanisms for verifying project consistency. These include:
- Checking whether data sources exist.
- Ensuring that all required fields for event patterns exist.
If Cogynt Authoring discovers any problems, it provides error messages describing the issues it found.
Performing Consistency Checks
Cogynt Authoring automatically runs consistency checks on active projects under the following circumstances:
- When the browser loads Cogynt Authoring.
- After making changes in a project.
Post-change consistency checks evaluate the entire project, not just the modified elements, because model artifacts are often related to each other or have various dependencies.
Note
Post-change consistency checks do not verify serialized diagram data for outcome computations and constraint computations, as it would require analyzing data stored as a third-party diagramming library. (This may change in future releases.)
The main application complements the post-change checks by doing its own verifications when a computation diagram loads.
Consistency checks are performed using a background task in a web worker. The task runs on a different process than the main application, so its execution does not affect application performance.
Identifying Errors
If Cogynt Authoring discovers any consistency errors, it displays a red circle next to the culprit path link in the application header panel. Model artifacts in different authoring environments may have their own consistency errors.
To check the details of errors:
- Click the affected model artifact.
- In the details panel, click Issues.
- Consult the description provided for each error.
Be sure to correct errors as necessary.
Warning
Cogynt Authoring does not permit deploying a model with consistency errors.