Skip to main content

StackJack 0.1.0.10185+748eb7d

StackJack 0.1.0.10185+748eb7d

This release makes spending limits on Foundry automations simpler and clearer, gives more useful error messages when connecting an agent credential, and fixes two display problems in the automation builder and on run pages.

Improvements

  • Foundry spending limits are now one optional dollar limit. Existing Foundry automations keep the limit they already had. New Foundry automations start with no limit, so turn it on in the builder if you want a cap.
  • Clearer results when a Foundry run hits its spending limit. The run is now shown as stopped at its spending limit, not as failed. The message on the run says the usage is billed through your Azure account.
  • More useful messages when connecting an agent credential fails. Five sign-in failures used to show a generic "please try again", even when retrying could not work. Each one now says what went wrong and what to do next. For example, if a typed instance address for HaloPSA or NinjaOne is not accepted, the message says so. If the sign-in could not be completed, the message tells you to start again and contact support if it keeps happening.

Bug fixes

  • In the automation builder, if you turned on the Foundry spending limit and then chose to discard your local draft, the switch could still show as on even though the saved automation had no limit. The switch and amount now reset to match the saved automation.
  • On a run that stopped at its credit limit, the run page and live view could show the automation's current credit limit, not the limit in force when the run stopped. This happened if the automation was edited after the run. They now show the run's own limit. If the run doesn't record that limit, they show a general "reached its spending limit" message.
ImprovedBug Fix