Delivery checks and troubleshooting | Mingcedar Studio

<div class="manual-doc-article manual-doc-article-section"><h2 id="tips">Tips: Delivery checks and troubleshooting</h2>

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

<div class="doc-card-list">

<article class="doc-card">

<h3 id="tips-item-1">Missing runtime asset</h3>

<p>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.</p>

</article>

<article class="doc-card">

<h3 id="tips-item-2">404 after navigation</h3>

<p>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.</p>

</article>

<article class="doc-card">

<h3 id="tips-item-3">Only one click works</h3>

<p>Check the button&#39;s Condition and saved behavior, then inspect runtime errors. Export and publish the latest package before testing again.</p>

</article>

<article class="doc-card">

<h3 id="tips-item-4">Template content not visible</h3>

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

</article>

</div>

</div>