{"version":"2.1.317","anchor":"routine-fire-queued-notifications-and-a-project-folder-name","canonical_anchor":"routine-fire-queued-notifications-and-a-project-folder-name","heading":"Queued notifications can be marked to open when a routine fires","tier":"internal","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/routine-fire-queued-notifications-and-a-project-folder-name","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Queued notifications can be marked to open when a routine fires\n\nQueued remote notifications can now be marked to open when a routine fires, and one server response gains an optional project folder name field\n\n**What**\n\nThere are two small additions:\n\n- Queued remote notifications can now carry a marker saying they open when a routine fires. Remote notifications are notifications that arrive from outside the session and wait in a queue. A routine is a task set up to run on its own. The marker is set only when every pending item in the queue passes a check.\n\n- One response from the server can now include an optional field called project_folder_name.\n\n**Why**\n\nBoth are details behind how routines and remote sessions are presented.\n\n- Area: Background Tasks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}