According to How does the bounty system work?, questions with bounties are removed from the "featured" tab once the bounty ends:

Questions with an active bounty appear with a special icon in all question lists, and are also visible on the home page's Featured tab.

During the grace period, there will be no indication in the questions lists (e.g. front page, featured tab) that the question has a bounty

However, the current behavior, at least in some instances, is that bountied questions are remaining on the featured tab beyond the seven-day bounty period.

On Biblical Hermeneutics.SE, a recently bountied question's revision history shows that the bounty ended two days ago (July 26, 08:47 UTC) and that it started on July 18 at 07:00 UTC:

BH.SE example question

Given this, the question should have been removed from the featured list on July 25, at the start of the grace period. As of this moment, however, the question still appears on the featured tab:

BH.SE featured tab

The problem is not limited to BH.SE. On Christianity.SE right now a question whose bounty was started more than 7 days ago, and which was already awarded, still appears in the featured tab:

C.SE example question

C.SE featured tab

Why are bountied questions not being removed from the featured tab exactly 7 days after their bounties start?

  • 1
    I also observed this in Spanish L&U. I awarded a bounty yesterday and the question is still featured. Jul 28, 2016 at 14:59
  • 1
    The funny thing is that the question showed as featured until just now, when a new bounty was started. Aug 2, 2016 at 8:18
  • 1
    @fedorqui Agreed, this is a consistent pattern: the question remains featured until a new bounty is started whereupon it falls off.
    – Susan
    Aug 3, 2016 at 1:58
  • 2
    Reproduced on Workplace, see this duplicate: Why does the Workplace's featured question tab show a question without a bounty?
    – Lilienthal
    Aug 9, 2016 at 6:20
  • 1
    More info: if there are others bounties offered, the question disappears from featured as soon as the bounty gets awarded. At least this happened here. Aug 9, 2016 at 14:21
  • 1
    Confirmed on Workplace: the second a new bounty is started, the old question disappears from the tab.
    – Lilienthal
    Aug 11, 2016 at 9:57
  • I've also experienced the issue on Hinduism.SE
    – Pandya
    Aug 12, 2016 at 5:21
  • 3
    Well, it's clearly a cross network bug, on each and every of the 150+ sites. Aug 12, 2016 at 5:42
  • 1
    Fully reproducible: I recently awarded a bounty on this question and it's still in the Featured tab. Seems like this cycle won't ever end and as @ShadowWizard mentioned all sites seem to be affected, though of course it will only be visible on the ones that don't constantly have active bounties
    – Lilienthal
    Aug 12, 2016 at 12:28
  • 3
    Reproduced on German.SE, Philosophy.SE, Astronomy.SE, Space.SE and Law.SE. See meta.stackexchange.com/questions/283404/…
    – wythagoras
    Aug 15, 2016 at 9:28
  • 1
    Reproduced on Retrocomputing.SE retrocomputing.stackexchange.com/?tab=featured
    – JAL
    Aug 18, 2016 at 15:16
  • Sites are being taken down for maintenance. Maybe it's being fixed? :hopeful:
    – wizzwizz4
    Aug 19, 2016 at 9:38
  • @wizzwizz4 nope. Sometimes bugs are left for years when they don't have critical impact. Aug 22, 2016 at 4:09
  • 1
    @Nathaniel You've hand-drawn-circled around the wrong "occured yesterday" on both pictures: that's the "notice removed", not the "end of bounty" notice.
    – wizzwizz4
    Aug 22, 2016 at 8:14

1 Answer 1


, as explained by Marc Gravell in his post on Retrocomputing Meta, this has been fixed.

it was everywhere, but it would only be observed if there was a site with an index that was changing from non-empty to empty, most commonly because the last "featured" question expired or was awarded. That means we wouldn't expect to see it on sites like stackoverflow, because that just would never happen

Thanks; there was a bug on the "tag engine" (the backend system that deals with this stuff) that failed to update the "count" of an index when that index was being reduced to zero (it is fine when reducing in general - just the zero case is the problem). This meant it was happily reporting data that it knew wasn't "featured" (or whatevever) any more. Essentially (not the actual code!):

// rebuild a filtered+sorted index...
int matches = workspace.ApplyFilter();
if(matches == 0) {
     // nothing to do
} else {
    index.UpdateCountAndCopyFromWorkspace(matches , workspace);

In the zero case, it would never actually mark the index as being empty (the "nothing to do" was wrong - it should still have updated the count). Entirely my fault. A permanent fix for this will deploy today.

  • 2
    Yeah, same thing. I found the bug on 4 meta sites, but missed it here. Aug 22, 2016 at 19:04

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .