Record the module name and installed version, UNA version, the page/action you used, what you expected and the exact error. Include when the issue began and whether it followed an update or settings change.
Use the relevant guide:
No Studio tile: confirm installation and activation completed, then verify the module's registered Studio records and packaged icon. Do not edit UNA core to hide an installation problem.
Update says the module was modified: preserve the files and compare them with the correct reference. Generated runtime files and deliberate modifications need review. Do not change the stored module version or replace the reference just to make the warning disappear.
Compatibility warning: compare the package declaration with your exact UNA version and dependencies. A successful check on one site is not universal compatibility certification.
An empty dashboard: zero records may be expected on a new site. Distinguish zero from unavailable data and from explicitly labeled preview figures.
A failed repair/recovery: stop, preserve the error and rollback evidence, and review the supported recovery procedure before repeating the operation.
Open Submit a ticket. Choose the affected product and Bug or Support request. Include:
Never include passwords, session/visitor access links, OAuth tokens, API keys, SMTP/IMAP secrets, private certificates or full production database exports in a public report.
These guides describe verified source/package workflows as reviewed on 2 October 2026. Menu names and feature availability can differ by installed version. The documentation does not announce a new release or change a module's Marketplace status.