Validation at Save

When you click Save in the configure dialog, StackJack doesn't just file your credentials away — it checks them for common mistakes, stores them securely, and immediately tests them against the vendor's API so you know right away whether the connection works.

What happens when you save

1. Pre-save checks. StackJack validates required fields and catches a handful of common, connector-specific mistakes before anything is stored (see below).
2. Secure storage. Credentials are written to Azure Key Vault (never to StackJack's database).
3. Plan activation. If this is the connector's first save, a Free subscription is created automatically.
4. Live validation. StackJack makes a real, lightweight call to the vendor API with your new credentials and records the result on the connector card.

The two outcomes

• Success — a toast confirms your credentials were saved and stored in Key Vault, and the card shows Valid. You're done.
• Saved, but validation failed (or timed out) — a warning toast tells you the credentials were saved but the live test didn't pass. The save is never blocked by a failed test — your credentials are stored, the card shows the problem, and StackJack automatically re-tests in the background. If you just created the credential in the vendor product, some vendors take a moment to activate new keys; if the failure persists, re-check the values against the setup guide.

Built-in mistake guards

The dialog blocks a handful of well-known misconfigurations before saving, with a specific explanation for each:

Timeouts and slow starts

Validation normally completes within about 15 seconds. CIPP is the exception: because CIPP runs on Azure Functions, a cold instance can take up to a minute to wake up, so CIPP validation waits longer before reporting a timeout.

Transient vs real failures

StackJack distinguishes between failures that mean your credentials are wrong and failures that mean the vendor was momentarily unavailable:

• Definitive failures (bad key, revoked token, missing permission) mark the credential Invalid and count toward auto-disable (see Connector Health & Auto-Disable).
• Transient failures (timeouts, vendor rate-limiting, vendor 5xx errors, a token refresh already in progress) are never counted against your credential — the background checker simply tries again later.