October 2026 Changelog

Covering releases from 1 to 14 October 2026. This entry will be extended at the end of the month.

October so far brings better controls for the approval queue, more ways to scope projects through an AI assistant, and fixes to project creation, attachments and catalog editing.

Pending Approvals shows the longest waits first

Pending Approvals now has page controls and a choice of how many rows to show. It starts with the longest-waiting approvals; click Time Waiting to reverse the order. Time Waiting now counts from when you were asked to approve, not from when the project was submitted. Canceled or declined steps, earlier steps replaced by a resubmission and archived projects no longer leave stale rows in the queue.

Early access

• Push to PSA V2. On accounts using Push to PSA V2, users whose role permits creating PSA pushes can choose Refresh PSA settings on the Push to PSA form for a project that has not been pushed yet, to update the cached lists without waiting for the daily refresh. That form shows when the settings were last refreshed, which lists failed to load, and a warning when no ConnectWise project boards were found. When you pick a Company on a ConnectWise or HaloPSA push and the client has no company mapping for that connection, the choice is saved for later pushes. An existing mapping is kept.
• Blueprints V2. For accounts using Blueprints V2, a fixed-hours governance item takes its catalog hours when the blueprint did not set its own, and a governance item with no resource takes the catalog resource. A standard resource with a zero rate in the blueprint takes the project rate table’s rate, while a nonzero saved rate is kept.

For integrators

• Retired MCP tools. The older MCP tools deprecated for removal on 30 September have been removed. Use the consolidated tools and the migration map for any calls in a custom client. list_service_categories remains available but deprecated.
• AI instructions for catalog services. Catalog services and subservices can carry AI scoping instructions through the API or MCP. MCP can return the instructions with catalog-service details and project scope. Use them for guidance, such as questions to ask or companion services to consider, and keep them out of client-facing text. Changing only AI instructions or guidance on an existing service no longer sends it back for approval.
• Rate tables and project phases over MCP. An assistant can now change a project’s rate table and list or add project phases, including a custom phase. Service writes can use the names of project-specific or renamed phases. Changing the rate table reprices standard resources and removes a resource if the new table has no rate for it.
• A default document template through the API. Set default: true on a document template through API v1 or v2 to pre-select it on new projects that don’t name a template, including projects created from the New Project form. Only one template per account can be the default. You can filter templates with filter[default].
• More complete v2 reads. V2 project, line-of-business and service-category reads keep their relationship links regardless of which include request filled the cache first. Product accounting codes can be read and written at /v2/products/{id}/product-accountings, and GET /v2/account now honors include and fields.

Fixes

• Password rotation stays off when you set it to zero. In Settings > Account Preferences, Password Rotation Interval now shows 0 when it is unset or disabled. Changing another preference no longer writes 90 into that field and turns password rotation on.
• Attachment types and failed uploads. Editing an attachment now also hides types already used by an active attachment on the project. If an archived attachment holds the type, the error tells you to restore it from Archived or choose another type. Upload validation now gives the reason a file could not be saved, and a failed upload attempts to remove the empty attachment so you can retry with the same type.
• CRM addresses when creating a project. Missing or whitespace-only address fields from a CRM opportunity now count as empty, so the form asks you to fill them in. If the location save fails, you see the reason and can retry without creating another project. ConnectWise opportunities now carry the site’s country with the address.
• Service locations in the project editor. In the current project services editor, the Location column now appears when the project has more than one active location, including a location no service uses yet.
• Service list and delete confirmation. The current project services editor reloads its service list when you reopen it after adding services. Deleting only subservices now counts the subservices in the confirmation, instead of saying you are deleting zero services.
• Product search and editing. In Settings > Product, starting or clearing a search returns to the first page. Saving a variable rate or accounting code keeps you on that tab instead of sending you back to Details.
• Restoring catalog services. Un-Archive on the Archived tab of the Professional Services and Managed Services catalogs now restores the service. It previously showed an error and left the service archived.
• Formatted contact phone numbers. When adding or editing project contacts, phone numbers with parentheses, dots, slashes and extensions such as ext. 21 are now accepted.
• Rejected ConnectWise reads. Rejected opportunity-list reads retain the last successful sync time and report the reason. A rejection (any 4xx response other than 408 or 429) puts the connection in Connection Error. ConnectWise opportunities now take the contact’s name, email, phone and title from one person: the opportunity’s contact, else the company’s default contact, else the bill-to contact. A failed PSA settings refresh keeps the last good lists, and rejection of every list marks the connection in error.
• Disabled CRM syncs stay stopped. CRM syncs stop when the connection or its CRM option is disabled, even if a job was already waiting to run.
• Version history and user reverts. New version-history entries from API v2 writes, including template uploads, are now recorded under the account. Reverting a user edit preserves sign-in fields instead of failing, and a conflict with existing data returns a validation message.

Getting Help

Have questions about any of these? Our Support Team is here to help.

📧 support@scopestack.io 📚 Visit our Help Center