<p class="no-margin">This article explains two common questions: why your <b>cloud stack</b> provider count may appear inconsistent across different views, and how <b>Link Lab</b> order delivery, refunds, and replacements are handled. Following these steps will help you confirm what you are billed for and what to do when a placement is delayed.</p><p class="no-margin">​</p><h1 id="h_9e4771fcaf"><b>☁️ Understanding Cloud Stack Provider Counts</b>​</h1><p class="no-margin">Cloud stacks report provider information in more than one place, and these views update on different schedules. It is normal to see a temporary mismatch.</p><ul><li><p class="no-margin"><b>List view (cs_list):</b> Shows a summary value such as <b>deployed_provider_count</b>. This field is cached and refreshes periodically, so it can briefly display <b>0</b> while deployment is still being indexed.</p></li><li><p class="no-margin"><b>Detail view (cs_get):</b> Shows the real-time state of the stack. This is the accurate, authoritative source for how many providers are currently active.​</p></li></ul><p class="no-margin">If <b>cs_get</b> confirms active providers (for example, 14) but <b>cs_list</b> shows 0, the detail view is correct. The list summary will catch up automatically, usually within 24 hours.</p><p class="no-margin">This list/detail display inconsistency is a recognized issue, and our engineering team has a UI correction for cloud stacks currently in development. It does not affect your active providers or your billing.<br>​</p><h1 id="h_03c132cf15"><b>💳 What This Means for Billing</b>​</h1><p class="no-margin">Billing is calculated from the authoritative deployment state shown in <b>cs_get</b>, not from the cached summary in <b>cs_list</b>. A <b>deployed_provider_count</b> of 0 in the list view does <b>not</b> reduce or increase your charges, and it does not mean your providers were removed.</p><p class="no-margin">To verify what you are being billed for:</p><ol><li><p class="no-margin">Open the cloud stack detail view (<b>cs_get</b>) and confirm the active provider list.</p></li><li><p class="no-margin">Compare that count against your current plan or invoice.</p></li><li><p class="no-margin">If the detail view matches your expectations, no action is needed even if the list summary still shows 0.</p></li><li><p class="no-margin">Wait up to 24 hours and refresh the list view to confirm the summary has synced.​</p></li></ol><p class="no-margin">If the detail view itself shows an unexpected provider count, or the list summary has not synced after 24 hours, reach out so we can investigate.<br>​</p><h1 id="h_e4d4ab841a">⚠️ Known Issue: Publishing Appears Stuck​</h1><p class="no-margin">When publishing a cloud stack, the assistant may appear to hang instead of confirming the order. This is a known issue, and the fix is complete and awaiting release. Because the failure is in the confirmation step, your order may actually have been submitted even though you did not receive a confirmation message — so do not assume it failed. Before re-attempting, open the cloud stack detail view (<b>cs_get</b>) to confirm the current state of your providers, and contact us if anything looks incorrect.</p><p class="no-margin">​</p><h1 id="h_87e4e53899">📦 How Link Lab Order Delivery Works​</h1><p class="no-margin">Link Lab placements are fulfilled by editorial and outreach partners, so delivery times vary by order. Each order has a standard delivery window, and most placements are completed well within it.</p><ul><li><p class="no-margin"><b>Standard window:</b> Placements are expected to be delivered within 30 days of order confirmation.</p></li><li><p class="no-margin"><b>Tracking:</b> You can monitor the status of each placement directly in your Link Lab order dashboard.</p></li><li><p class="no-margin"><b>Partial delivery:</b> An order may be partially fulfilled, meaning some placements go live before others.​</p></li></ul><h1 id="h_19c357bc5b"><b>⏳ When a Placement Is Late or Undelivered​</b></h1><p class="no-margin">If one or more placements in an order pass the 30-day delivery window without going live, you are entitled to a <b>replacement</b> or a <b>refund</b> for those specific placements.</p><p class="no-margin">To request this, please have the following ready:</p><ol><li><p class="no-margin">Your <b>order number</b> (for example, #24380).</p></li><li><p class="no-margin">The specific placements that remain undelivered.</p></li><li><p class="no-margin">Your preference: a <b>replacement</b> placement of equal value, or a <b>refund</b> for the undelivered items.</p></li></ol><p class="no-margin">Only the undelivered placements are affected. Placements that were already delivered within the order remain valid and are not refunded.</p><p class="no-margin">​</p><h1 id="h_bc184a5437"><b>🔄 Refund and Replacement Timelines</b>​</h1><ul><li><p class="no-margin"><b>Replacements:</b> A new placement of equal value is queued and follows a fresh 30-day delivery window.</p></li><li><p class="no-margin"><b>Refunds:</b> Approved refunds are issued back to your original payment method and typically appear within one billing cycle.​</p></li></ul><h1 id="h_084319850a"><b>✅ Quick Troubleshooting Checklist</b></h1><ul><li><p class="no-margin">Provider count shows 0 in the list but correct in detail view? <b>Trust the detail view</b> and allow up to 24 hours to sync.</p></li><li><p class="no-margin">Worried about billing? <b>Confirm the active providers in cs_get</b> before raising a concern.</p></li><li><p class="no-margin">Publishing seems stuck without confirming the order? <b>Check cs_get</b> for the stack's current state before retrying, in case the order already went through.</p></li><li><p class="no-margin">Placement past 30 days? <b>Gather your order number and undelivered items</b>, then request a refund or replacement.</p></li><li><p class="no-margin">Detail view also looks wrong, or sync did not complete? <b>Contact us</b> for a manual review.</p></li></ul>