[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-changelog\u002F2026-09-27":3,"docs-tabs-changelog\u002F2026-09-27":6},{"content":4,"lastmod":5},"# API changes: September 27, 2026\n\n[← Changelog](\u002Fdocs\u002Fchangelog) · [September 2026](\u002Fdocs\u002Fchangelog\u002F2026-09)\n\n### FIX-0927-3: business process operations on an account without the module answer 409 instead of 404\n\n**Before**\n\nOn an account where Business Processes are not included in the plan or are switched off in settings, only the list of running workflows answered `409 BIZPROC_MODULE_NOT_ENABLED` — [GET \u002Fv1\u002Fworkflows](\u002Fdocs\u002Fautomation\u002Fworkflows\u002Flist). The other four operations of the section answered `404 ENTITY_NOT_FOUND` in the same account state: [POST \u002Fv1\u002Fworkflows\u002Fstart](\u002Fdocs\u002Fautomation\u002Fworkflows\u002Fstart), [DELETE \u002Fv1\u002Fworkflows\u002F:id](\u002Fdocs\u002Fautomation\u002Fworkflows\u002Fterminate), [POST \u002Fv1\u002Fworkflows\u002Factivity-log](\u002Fdocs\u002Fautomation\u002Fworkflows\u002Factivity-log) and [POST \u002Fv1\u002Fworkflows\u002Fevent](\u002Fdocs\u002Fautomation\u002Fworkflows\u002Fevent). That answer looked like a wrong template, document or workflow ID, although the IDs were correct.\n\n**After**\n\nAll five operations of the section answer the same way in this account state: `409 BIZPROC_MODULE_NOT_ENABLED`. The message names the Bitrix24 method that was called, both possible causes and the action to take: ask an account administrator to enable Business Processes. Other errors of these operations are unchanged.\n\n**Impact on integrators**\n\nNo action is required: the refusal was a 4xx and stays a 4xx, and the former `404 ENTITY_NOT_FOUND` was never documented for this state. Retrying with other IDs does not help while Business Processes are unavailable on the account. For stopping a workflow, `404 ENTITY_NOT_FOUND` still means the workflow instance was not found, while `409 BIZPROC_MODULE_NOT_ENABLED` means the module is unavailable and the workflow was not stopped. An integration that treated 404 as a sign of an already finished workflow now sees 409 on such an account, and the workflow is not stopped.\n\n### NEW-0927-5: Checklist actions and attaching a file to a task\n\nTen named `\u002Fv1\u002Ftasks\u002F:taskId\u002Fchecklist\u002F...` and `\u002Fv1\u002Ftasks\u002F:taskId\u002Ffiles\u002Fattach` routes are now available for saving a tree, managing members, moving and completing checklist items, managing checklist attachments, and attaching a Disk file to a task. Each route returns the Bitrix24 method result in `data`.\n",null,{},1794739481303]