{"version":"2.1.287","anchor":"job-reply-distinguishes-a-booting-session","canonical_anchor":"job-reply-distinguishes-a-booting-session","heading":"Replying to a job that is still starting now says so","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/job-reply-distinguishes-a-booting-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Replying to a job that is still starting now says so\n\nReplying to a job whose session is still starting now fails with ERESPAWNING instead of ENOREPLY\n\n**What**\n\nA job is a task that runs in its own session. Replying to a job whose session is still starting now fails with the code `ERESPAWNING` and the error \"the session is still starting\". Previously it always failed with `ENOREPLY`, saying the job is not accepting replies.\n\n**Why**\n\nA program sending replies can now tell a session that is still starting apart from a real refusal, and try again a little later.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}