A shopper says a linked code was refused

Check where the campaign stands on the Campaigns list: a code is refused while its campaign is switched off, before its start and after its end. On a per-visitor campaign, the code works only for a visitor who has been shown the timer, and only for that visitor's own length of time. A visitor whose browser has JavaScript switched off, or who clears their cookies, may have no start recorded, and is refused. So is a start more than five minutes ahead of your site's clock, which a cookie edited by hand can carry. A device whose clock is more than five minutes fast records such a start too, so its shopper is refused until your site's clock is within five minutes of it; the code then works for the campaign's length from that start. The code goes by your site's clock and the timer by the shopper's device, so on a device whose clock is wrong the timer can end earlier or later than the code, by up to as much as the clock is out. On a campaign that repeats daily or weekly, a countdown that started before midnight, or before Monday, still counts until it ends. Staff adding the code to an order by hand, in wp-admin or through the REST API, are never refused; at the shop's own cart they are refused like anyone.