{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/90a4f54b340f4873ba78d0546d1caf7e\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/90a4f54b340f4873ba78d0546d1caf7e-de3d3668c3b4322b.gif","duration":148.458667,"title":"Bulk Task Status Updates, Completed Restricted","description":"This Loom explains the updated Bulk Task Status Updates functionality and which statuses can be edited in bulk. It notes that tasks can have multiple statuses, including system statuses Pending, New, Completed, and Archived, plus custom statuses. Completed is not available for bulk updates because moving from Pending to Completed can trigger many dependencies such as registration details, formation dates, company name updates, and creation of next annual compliance tasks. Teams can bulk update other statuses like Archived, Gathering docs, any custom status, and pending and delayed new. It suggests teams can create a custom status like complete or finished to communicate completion without relying on the system confirmation tied to dependencies."}