StackJack 0.1.0.4023+174939d

This release makes the region-move experience honest and self-healing, opens 16 previously Business-only CIPP tools to Pro, and clears up several connector error and validation messages that were sending people down the wrong path. It also raises agent run throughput so scheduled runs no longer wait on each other.

New features

• After an unsuccessful region move, AI client connections and authorizations that were switched off while the move was in progress are now restored automatically. Previously these stayed dead with no self-service way back and had to be restored by support.

Improvements

• 16 CIPP tools (cross-tenant analytics and operator-class utilities) are now available on the Pro plan. No tool on any connector requires a plan above Pro.
• at_create_task_note now lists all of its required fields, including the note type, and points to the tools you can use to discover the valid note-type values for your Autotask instance. It also warns that task note types are a separate list from ticket note types, so a value copied from the ticket-note tool may not exist.
• cipp_list_exo_request descriptions now match what the tool actually enforces: only canonical read-style cmdlets are accepted, and that restriction is enforced rather than advisory.
• Published product documentation and tool metadata now reflect the current tool descriptions and plan tiers, rather than a previous state of the catalog.

Optimizations

• Agent run capacity is substantially higher, and scheduled agent launches no longer serialize behind each other. Previously a single scheduled launch could hold up launches for unrelated tenants; runs now start promptly when several are triggered at once.

Bug fixes

• A region move that failed no longer renders as if it had never been attempted, and no longer looks like it succeeded. The region move page now shows a failure notice naming the attempted destination and a stable reference code you can quote to support, with the option to start a new attempt still available.
• Tenants with a previous unsuccessful region move now keep access to the page explaining what happened, instead of getting a "page not found" screen.
• Connector errors where the vendor itself reports an expired session are no longer misread as a revoked authorization. Previously these could tell you to re-run the whole connector reconnect flow for a failure that resolves on its own.
• Adding a user to a team no longer reports success and sends an invitation when the account could not actually be added because of a conflicting identity record. The portal now names that specific condition, and sign-in and connector authorization surface a clear message in the same situation instead of appearing to work and then failing on later requests. The message also warns against creating a second account, which makes the condition worse.
• The note-type check on Autotask task note creation now recognises the field regardless of how it is capitalised, and treats empty or blank values as missing, so those calls are caught with a clear validation error instead of an opaque vendor error.

UI & UX changes

• The region move failure notice is now accurate for the stage the move reached. It no longer tells every tenant that nothing was moved; where a copy may have been written to the destination, it says so, confirms that no data was deleted and that the current region is still the active home, and explains that the inactive copy is cleaned up.
• The same notice now labels the timestamp as when the move was started rather than when it stopped, warns that connected AI clients may have been switched off and can be restored by support, and — in cases where the destination may still hold data from the previous attempt — asks you to contact support before retrying instead of inviting an immediate retry.
• If a move could not be started at all, that now gets its own short notice confirming nothing was changed, rather than showing no feedback after confirming.
• The Business upgrade card no longer advertises access to Business-tier tools, which no longer exist. The call cap and per-user OAuth/team bullets remain, since those are what the plan actually adds.