StackJack 0.1.0.8780+af661ce

This release makes ConnectWise project creation more reliable and lets Azure AI Foundry setups that deploy only non-Claude models run on more subscription types. It also makes automation Re-sync and Repair more dependable, fixes several cases where the wrong connection was used, and improves region moves.

Improvements

• Azure AI Foundry setups without Claude: A turnkey Foundry setup that deploys no Claude model can now use CSP, trial, and spending-limit subscriptions, since Azure sells its other models on them. These setups also skip the Anthropic terms step. When a setup does deploy Claude, StackJack checks the subscription again before deploying, including on a retry.
• ConnectWise project tools: The project creation tool now lists all six fields ConnectWise requires and shows the expected format for each. Other project write tools, such as team members, project tickets, phases, and notes, now describe their required fields and reference formats correctly. Agents should get project creation right on the first try more often.
• Clearer ConnectWise write errors: When ConnectWise rejects a create or update because a field has the wrong format, the error now names the field and its expected shape. It is also no longer marked as safe to retry unchanged, so agents stop re-sending the same failing request. Transient server errors on reads are still retryable.
• Re-sync repairs automation credentials: Re-sync now checks all of an automation's credentials and replaces only the ones that no longer work. This includes credentials rotated or revoked on the MCP Setup page. Healthy credentials are left alone, so pressing Re-sync no longer rotates a working credential. If StackJack can't check a credential because of a temporary storage problem, it changes nothing and marks the automation as needing a re-sync.
• Re-sync for Foundry automations: Re-sync now also applies credential fixes to Foundry automations that are already running.
• Run-as changes apply everywhere: Changing the person an automation runs as now also updates the credentials used for its read steps. Before, those steps could keep acting as the previous person.
• Live tool tests in the guided builder: Live tool tests run during an automation interview now use only tools that the person building the automation has access to.
• Region move messages: The pre-move checks and refusal messages on the region move page now use plain product language. Where you can't fix a problem yourself, the message tells you to contact StackJack support.
• Region move cancellation: If a cancel request collides with another change, you now see an accurate answer based on the move's current state, and the page refreshes. Before, you could be asked to press Cancel again when the move had already been cancelled.
• Foundry wording: The Foundry tab, the setup steps, and related messages now name the supported model families (Claude, GPT, Grok, DeepSeek, Llama, Mistral, and more) instead of reading as Claude-only.

Bug fixes

• Repairing an existing automation rebuilt it without its attached knowledge until the next save. Repair now keeps the automation's knowledge.
• Repairing an automation whose knowledge made the prompt too large returned a generic server error, after the existing setup had already been removed. The size is now checked first, and you get a clear error with nothing removed.
• Re-sync and Repair are now refused while your organization is moving between regions, with a message explaining why. Before, they could remove resources the move depends on. If an automation is left in a failed state by a move, its Repair button stays available once the move finishes.
• Test connection, Capture live, and live tool runs that don't name a connection now use the connection marked as your default. Before, after you removed your original connection or chose a different default, they could use the old connection or report that no credentials were found.
• When you pick the original connection explicitly in live tool testing, that connection is now used.
• Saving an automation credential could report "No credentials found" even though the enrollment succeeded. This no longer happens.
• If your default connection for a connector is disabled but another connection for that connector is enabled, calls that name the enabled connection now go through. Calls that name no connection get a clear error explaining the default is disabled, instead of a generic "no credentials configured" message.
• On the Team page, editing a member's Autotask identity when your connections can't be loaded now blocks the edit and explains why. Before, it could save the value to the wrong connection.
• A region move that stalled could leave your organization read-only, with its connections switched off, past the one-hour limit. The limit is now measured from when the move actually began, so a stalled move ends and your organization is restored on time.
• Cancelling a region move at an early stage could leave your MCP connections switched off. They are now reliably restored.
• A cancelled or failed region move now restores only the connections that move switched off. Connections you had turned off yourself stay off.
• Automation postconditions that match a pattern against very long values (over about 100,000 characters) could report a false failure. They now evaluate correctly.
• Installing an automation template with parameter validation could occasionally be refused as having an invalid pattern when the system was busy. This no longer happens.

Breaking changes

• Creating, editing, or deleting automations through the AI builder tools now requires a connection tied to a specific person. Endpoint keys created on the MCP Setup page are organization-level and are refused for these changes. Instead, either:
• connect your AI tool with just the endpoint URL from the MCP Setup page and sign in with your own StackJack account, or
• make the change on the Automations page.

Fixed customer-reported issues

• Creating a project in ConnectWise through StackJack failed because required fields were missing or sent in the wrong format (01M3MM9E2C079JGSJFQMTJATNZ). The project creation tool now lists every required field and its expected format. If ConnectWise still rejects a field, the error names the field and tells the agent not to resend the same request.