{"version":"2.1.246","anchor":"background-jobs-with-a-duplicate-name-get-a-numbered-suffix","canonical_anchor":"background-jobs-with-a-duplicate-name-get-a-numbered-suffix","heading":"Background jobs with a duplicate name get a numbered suffix","tier":"notice","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/background-jobs-with-a-duplicate-name-get-a-numbered-suffix","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Background jobs with a duplicate name get a numbered suffix\n\nBackground jobs with clashing names get a numbered suffix so you can tell them apart.\n\n**What**\n\nBefore a background session starts, its name is checked against the names of existing jobs and, if it clashes, is given a suffix like ` (2)`. Repeat clashes read the existing number back out and increment it.\n\n**Details**\n\n- The seed records that the name came from a collision rather than being chosen directly.\n- Renaming is best effort: if the list of existing jobs cannot be read, the original name is used as is.\n\n**Evidence**\n\n`nameSource: \"collision\"`\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}