read thedocs.

[ docs // guides & reference ]

Connector setup guides, tool references, auth flows, and platform concepts — everything you need to run StackJack, in one place.

Browse the Docs All Connectors
34 connectors documented // 6,712 tools referenced // setup, auth & platform guides
↓

No pages match that search. Clear it

← All documentation

Editing an Automation

The edit form lets you change everything about an existing automation — its identity, instructions, trigger, guardrails, tool access, and active state. Open it with the Edit button on the automation detail page.

If the automation was created in the Advanced Builder, a Switch to advanced builder link appears at the top of the form — use it when you would rather edit through the step-by-step Builder (with its knowledge and capabilities steps) instead of the flat form.

What you can change

Field Notes
Name / Description The automation's display identity.
System prompt The standing instructions the agent runs with.
Trigger On demand, Scheduled, or Webhook — with the matching sub-editor (see Triggers: On-Demand and Scheduled and Webhook Triggers). Switching trigger type resets the trigger-specific settings.
Max runtime (seconds) Per-run wall-clock limit. Must be between 30 and 3600 seconds (default 300).
Max credits per run Per-run spending cap. Must be between 0.01 and 500 credits (default 50).
Dry run mode When checked, write-capable tools behave as read-only — safe for testing.
Active Uncheck to disable the automation (it cannot run while inactive); re-check to re-enable it.
Email me when a run fails When checked, StackJack emails you each time one of this automation's runs reaches the Failed state.
Notification email The address failure emails are sent to. It appears only when "Email me when a run fails" is checked, and while that toggle is on a valid address is required to save.
Allowed tools The automation's tool allow-list. At least one valid tool is required to save.
Consent If autonomous operation was never accepted for this automation, an "I accept autonomous operation risk" checkbox appears here so you can accept it as part of the save.

Fixing stale tools

If your plan changed or a connector subscription was cancelled since the automation was configured, some of its allowed tools may no longer exist in your tenant's catalog. The tool selector surfaces these as a warning with removable chips:

  1. Review the stale tool names listed in the warning banner inside the tool selector.
  2. Remove them one at a time, or click Remove all invalid.
  3. Save changes stays disabled until at least one still-valid tool remains selected — a selection made up only of stale names cannot be saved.

If the stored tool configuration is unreadable altogether (a legacy format or corrupted data), the form shows Tool configuration unreadable (SJ-AGENT-TOOLS-FORMAT) — pick a fresh set of tools and save to repair the record.

Banners you may see

  • Sync drift detected (SJ-AGENT-SYNC-NEEDED) — the remote state may differ from what's shown; saving re-synchronizes it.
  • Remote resources orphaned (SJ-AGENT-ORPHANED) — the automation's remote resources are missing; saving may fail. Consider deleting and re-creating.
  • Schedule drift — context-sensitive copy for scheduled automations; in most cases an edit-save here clears it.
  • MCP harness exposure flag cleared (info) — shown once when an older automation carried the "expose to external AI harness" flag on a non-on-demand trigger. That combination is no longer valid; the flag is cleared automatically and persisted as off on your next save. No action needed.

Saving

  1. Click Save changes. Client-side checks run first (runtime and credit bounds, at least one valid tool).
  2. On success you return to the automation detail page.
  3. On failure, the form shows a specific message:
Support code Meaning
SJ-AGENT-SAVE-FORBIDDEN Your tenant is not permitted to edit this automation.
SJ-AGENT-SAVE-NOT-FOUND The automation was archived or deleted before the save completed.
SJ-AGENT-SAVE-UNAVAILABLE The automation service could not be reached — retry in a moment.
SJ-AGENT-SAVE-UPSTREAM-REJECTED Anthropic rejected the update — check the settings and try again.
SJ-AGENT-SAVE-SERVER-ERROR Unexpected error — retry; contact support if it persists.

Validation messages (for example "Select at least one tool before saving.") are shown verbatim.