StackJack 0.1.0.5946+67d2dfb

This release corrects how bundle changes report and calculate refunds and credits for unused time, fixes an immediate-cancellation failure, tightens Autotask member identity mappings to the connection they were confirmed against, and closes several reliability gaps in automation write steps and Avanan credential handling.

Improvements

• After a bundle change completes, the confirmation message now states what actually happened to your money: refund pending, refunded, credited to your account, rejected by the payment provider, or no adjustment needed. Previously the message could claim a credit when nothing had been billed, and a rejected refund could read as still pending.

Bug fixes

• Immediate cancellation could be refused with an error about an uncomputable credit when a tier change or term-end removal had been billed as a catch-up across billing periods of different lengths (for example, a change made just after a 31-day month renewing into a 28-day one). Cancellation now proceeds in these cases.
• The refund or credit for unused time on a bundle change is now calculated against the period each charge actually paid for. Previously a catch-up charge for a prior period could be treated as covering future time, producing an incorrect adjustment.
• Autotask connector credentials could be automatically disabled after a disconnect-and-reconnect sequence for the Avanan connector left a stale internal record behind; routine validation checks no longer count that condition as a credential failure, and a reconfiguration can no longer race ahead of a disconnect.
• On the Team page, an administrator can now see and remove a member's Autotask identity mapping that no longer applies (for example, one confirmed against a connection that has since been replaced). Previously the mapping was hidden and only the member could clear it from their own Connectors page.
• On the Team page identity dialog, values that finish loading after the dialog opens no longer overwrite an entry the administrator has already edited.
• Automations running in dry-run mode: a write step is now refused if its credential's dry-run setting no longer matches the automation's, so a real change cannot be made during a dry run (and a simulated change cannot be reported as carried out after switching to live).
• Automation write steps are no longer issued under a deadline too short to complete, which could previously leave an irreversible call cut off mid-flight and recorded as finished without retry.
• Automation write steps now refuse to run when more than one live write credential exists for the same automation, and credential re-derivations for one automation are processed one at a time from the latest saved settings.

UI & UX changes

• In the connector removal dialog, the immediate-removal option is now labelled "Remove it now and give back the unused time" rather than describing it as a refund, since the outcome can be a refund, an account credit, or no adjustment depending on what was billed.

Breaking changes

• Autotask member identity mappings now apply only to the specific connection they were confirmed against. If you disconnect Autotask and connect a different account under the same connection name, existing mappings become inactive rather than carrying over to the new account. Any mapping that has not been confirmed against its current connection will not apply until it is re-saved on the Team page or the member's Connectors page.