Skip to content

Delivery checks and troubleshooting

Check page names, resources, template values, and behavior targets before publishing; troubleshoot runtime results in Mingcedar.

TipsDocumentation revised: 2026-10-21

Tips: Delivery checks and troubleshooting

Check page names, resources, template values, and behavior targets before publishing; troubleshoot runtime results in Mingcedar.

Missing runtime asset

If a required runtime asset is missing, confirm the full screen package was published and the menu points to its HTML entry. Ask the Mingcedar administrator to check shared runtime resources if the issue remains.

404 after navigation

Check whether the target is a PowerPoint page, exported file, relative path, Mingcedar screen, or external website. The target type and path must match the exported files.

Only one click works

Check the button's Condition and saved behavior, then inspect runtime errors. Export and publish the latest package before testing again.

Template content not visible

Confirm exported template assets, placeholder values, popup scope, and menu entry are present in Mingcedar.

Click the image again or press Esc to close