Plan how an expired offer stops on a disconnected screen

Identify what the player can retain

DigitalSignage.com documents that its SignPlayer can continue cached content during an internet outage while new updates wait for reconnection. Its guidance also distinguishes live feeds from downloaded media. These are product-specific behaviors checked on November 7, 2026, not guarantees for other players or every deployment.

Inventory the media, schedule and data dependencies for the actual campaign. Ask the operator which parts are downloaded, streamed or read from an external page. Determine whether the player has already received the approved expiry schedule and fallback. A central schedule that has never reached the device cannot control its disconnected behavior. Mark the last verified synchronization separately from the last time someone saw the screen.

Design the end state before the offer starts

Choose what should appear after the offer expires, including during a prolonged outage. An evergreen brand message may be appropriate; an unchanged promotional price may not. Ask the supplier to verify how the actual player behaves when no scheduled content remains. DigitalSignage.com's documentation warns that its player may retain the last cached content when no valid campaign remains, which makes an assumed blank-screen fallback unsafe.

Have the implementation owner test the local clock and expiry behavior under approved conditions. Include time-zone boundaries, reboot after expiry and a fallback that has not finished downloading. Do not solve a withdrawal problem by silently extending the commercial offer. If the available system cannot enforce the required end state, choose less time-sensitive content or a placement with a supported withdrawal method.

Separate a remote request from confirmed withdrawal

Create status labels that describe observable events: withdrawal requested, player reached, replacement downloaded and replacement observed. Avoid a single completed checkbox for a fleet with mixed connectivity. A missing heartbeat means the management system cannot currently confirm the device state; it does not prove the screen is black or that the expired message has stopped.

Agree an authorized local contact route for unresolved screens. Site staff may be able to confirm the displayed message or follow the operator's approved procedure, but marketers should not improvise electrical, access-control or network changes. Prioritize screens carrying consequential stale claims. Preserve a proportionate record of the affected screen, last known content and next verification step without collecting footage of customers or unrelated private activity.

Verify recovery without reintroducing the old campaign

When connectivity returns, check which publication version reaches the player and what appears after synchronization finishes. An online badge alone is not the acceptance test. Inspect the intended replacement and the next relevant playlist transition, using supported evidence or an authorized site check. Confirm that a restored old backup or queued publication does not bring the retired offer back.

Review the incident against the preflight plan. Was the fallback missing, the expiry misunderstood, the device clock wrong or the withdrawal merely unobservable? Repair the specific cause and test it on a controlled fixture before another time-sensitive campaign. Keep the campaign record factual: some screens may have been verified promptly while others remained uncertain. Do not convert uncertainty into either a success claim or an unsupported accusation of continued display.

Make the reasoning concrete.

A fictional chain publishes a weekend discount and then removes it centrally on Monday. Two lobby players are offline, and the team has no evidence that they downloaded a replacement or an effective local expiry rule.

The chain keeps the two players as unresolved exceptions and uses its authorized site contacts to verify the display. Future offer releases include an offline expiry rehearsal.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Cache

   Which campaign components remain usable without a connection?

2. Receipt

   What proves the player received the expiry schedule and fallback?

3. End state

   What appears when the campaign expires with no network available?

4. Withdrawal

   Which requested, downloaded and observed states are still unresolved?

5. Recovery

   How will reconnection be checked for stale content returning?

Watch for the wrong conclusion.

• Equating an offline badge with a dark screen.
• Assuming deletion in the CMS deletes every local copy immediately.
• Using an untested empty playlist as the withdrawal strategy.

Sources & scope

Workflows, worksheets and fictional examples are original editorial analysis, not supplier implementation instructions or measured business results. Sources support only the specifically attributed platform facts. Supplier controls, contracts and local requirements can change; verify the actual placement and current provider guidance before implementation.

• DigitalSignage.com: What happens when the internet goes down →Primary platform documentation · Supports: Supports SignPlayer-specific cached playback, delayed new updates, local expiry and possible last-content retention when no valid campaign remains; operational withdrawal plan is editorial.