{"version":"2.1.228","anchor":"self-hosted-runner-waits-for-the-turn-that-follows-a-backgro","canonical_anchor":"self-hosted-runner-waits-for-the-turn-that-follows-a-backgro","heading":"Self-hosted runner waits for the turn that follows a background task","tier":"notice","area":"Self-Hosted Runner","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/self-hosted-runner-waits-for-the-turn-that-follows-a-backgro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Self-hosted runner waits for the turn that follows a background task\n\nA session still owing a report after a background task stays alive instead of being treated as idle.\n\n**What**\n\nA session whose background task has finished but which still owes one more turn to report the result now counts as waiting on you, so the runner keeps it alive instead of treating it as idle.\n\n**Details**\n\n- Appears in the `[runner:session]` debug log as \"finished background task awaiting the follow-up turn\", next to the existing live-task and wakeup reasons.\n- Driven by a new callback the session uses to declare that a follow-up turn is pending.\n\n**Evidence**\n\n`finished background task awaiting the follow-up turn`\n\n- Area: Self-Hosted Runner\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}