Jev integration setup failure

Classify an integration setup failure from its reported state

Provide the error reason, retry state and precomputed duration. Compare reauthentication, a changed integration and a transient failure under the displayed four-week rule.

integration setup failureLive API
Try an example

The temporary error is still retrying within the stated duration.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This original error-reading exercise adapts the setup-failure categories in ha-gutcheck, linked by the source post. The errors and duration buckets are synthetic. The demo does not retry an integration, sign in, remove anything or diagnose physical equipment.

Using the reported error, state and duration: Reauth for explicit invalid, expired or revoked credentials; Changed for an explicitly removed/unsupported service, or a timeout-type failure lasting over four weeks or stopped in setup error; Transient for a temporary timeout/offline/busy/rate-limit reason still in setup retry for at most four weeks.

Decision rules and labels
ReauthChangedTransientUnclear
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

What the decision checks

The same timeout text can lead to different review categories depending on whether retries continue and how long the failure has been observed. The duration bucket is computed outside the model.

Changed is a review label under this disclosed policy, not proof that hardware is permanently broken. A setup-error state means automatic retries stopped; a restart or reload may still recover it. Reauth identifies reported sign-in trouble without guaranteeing a fix.

This original error-reading exercise adapts the setup-failure categories in ha-gutcheck, linked by the source post. The errors and duration buckets are synthetic. The demo does not retry an integration, sign in, remove anything or diagnose physical equipment.

Illustration of one spreadsheet row producing two separate classification results
Illustration of the decision flow.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for integration setup failures.

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Provide the error reason, retry state and precomputed duration.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between Reauth, Changed, Transient, Unclear. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

    Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review Unclear before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Short timeout retryTransient100%
Revoked tokenReauth100%
Service retiredChanged100%
Long timeoutChanged95.0%
Stopped tryingChanged83.0%
Unexplained failureUnclear93.0%

These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified

Understand the results

Integration setup failures: six recorded examples

The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.

Using the result in your application

The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.

Replay options

Inspect saved outputs or request a new decision

View the code example
Two independent commands
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json

# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.
Scope of this demo

Where this decision fits

Useful scope

  • Organizing setup-error queues
  • Separating reported credential failures
  • Combining reason text with retry state

Outside this demonstration

  • Retrying, reauthenticating or deleting integrations
  • Diagnosing hardware failure
  • Using real passwords or tokens as inputs
Example FAQ

Using this example

The input contract and these limits define what the result means.

Does Changed authorize removing the integration?

No. It calls for separate review of the stated setup. The application should preserve configuration and require an explicit decision for any change.

Should I include the failing API key?

No. The error category is enough. Use redacted error text and a symbolic credential description; a secret value adds no useful evidence.

Does the leading probability measure accuracy?

It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.

Will a result change an external system?

No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.

Test a different input

Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.