Resolve a problem
Identify what failed before trying again.
The outcome
Choose the right action: correct, reconnect or ask for help.
INPUT_ERRORCorrect the inputsAUTH_ERRORRestore the connectionAPI_CHANGEDReview the repairEXECUTION_ERRORInspect the outcomeUnknown write outcome? Check the site before retrying.
Your path, in three steps.
- 01
An input is incorrect
INPUT_ERROR: check fields, formats and whether the requested record exists.
- 02
The software refuses access
AUTH_ERROR: open the reconnection flow and complete the checks requested by the software.
- 03
The behavior changed
API_CHANGED: inspect the repair and its result. EXECUTION_ERROR: use execution details to understand the issue or contact the team.
Want to go deeper?
Open just the topic you need.
Overview
Websites change without telling anyone, and accounts get signed out. Find your symptom below: what you see, why it happens in plain words, what to do about it, and what the result should look like.
01 · THE SESSIONYour access to the site
Its lifetime depends on the software. The connector can refresh it when that flow is supported.
02 · CREDENTIALSSaved with your permission
They can allow a fresh sign-in. Additional verification may need your involvement.
Each installation keeps its own access.
What Vela does by itself
- It tries each reading connector about once an hour, to catch problems before you do. This costs you nothing and does not count as a use.
- It never tries connectors that change things. A check that books an appointment is not a check. Where a site offers a way to verify the sign-in on its own, that is what is tried instead.
- If the problem is just a sign-in and you saved your password, it signs in again and moves on — you are not told, because nothing happened.
- If the site genuinely changed, it rebuilds the connector from your original recording and checks the new version before switching to it.
- The previous version is always kept, so you can go back.
- Retry repair on the connector page asks it to try again — use it once, and read the history before pressing it a second time.
A repair never redoes your action
Vela never books, sends or submits anything to test a connector. It replays the recording instead.
The connector says the sign-in failed
| Symptom | What it means | What to do | Expected result |
|---|---|---|---|
| A banner on the connector page says the connector could not sign in, with a button Open sign-in browser. | The site logged the connector out. This is normal and expected, not a fault in your connector. | Click Open sign-in browser and follow Sign a connector back in. | The page reports Session restored, and a Check health run then succeeds. |
| The run history shows an authentication failure while the connector still looks healthy. | The site's own permission expired inside the session Vela holds. The connector record is fine. | Reconnect it once from the connector page, not from your tool. | The next call from your tool returns an answer instead of an authentication error. |
| An e-mail asks you to sign in again for one named connector. | Vela tried to sign in by itself once, that attempt needed a person, and it stopped rather than guessing. | Use the link in the e-mail. It leads to the same page as the button. | The reconnection page reports the session restored. |
A connector could not be created or will not build
| Symptom | What it means | What to do | Expected result |
|---|---|---|---|
| Start building stays grey and will not respond. | The screen needs the address and the goal before it can start. In Advanced · Define your fields it also needs at least one output and an example for each input. | Fill the missing field. The line next to the button names it. | The button turns active and the build starts. |
| A build stops because of an anti-robot check. | The site is built to refuse automation on purpose. This is out of scope, and no amount of retrying changes it. | Stop there. Choose a different site or a part of the site that does not ask for that check. | Nothing to expect — this case is a genuine limit of the product, not a step you missed. |
| A build stops on a step only some accounts have. | The demonstration took a route your account does not have available, or a step appeared that Vela did not recognise. | Run the demonstration again, stay on the shorter route, and take that step yourself when it appears. | The build continues past the step and reaches the end. |
| A build finishes but the result is empty or wrong. | The demonstration taught Vela from a search with no results or a made-up value, so it never saw what a real answer looks like. | Run the connector in the API Playground on a record that really exists, and rebuild if the shape of the answer is wrong. | The run returns the values you expect. |
A connector is no longer available
| Symptom | What it means | What to do | Expected result |
|---|---|---|---|
| A call is refused with the connector reported as unavailable or not found. | The connector was deleted, paused, or the key used by your tool no longer matches. | Check the connector still exists under Connectors and is switched on. If it exists, refresh the key in Integrations & Exports and paste the new one into your tool. | The call returns an answer, and the run appears in Activity & Logs. |
| The connector runs but reports that a value was not found. | The site was asked and said no — a name that does not exist, a slot already taken. The message usually lists values that would work. | Send a value that really exists on the site. | The run returns the record instead of the refusal. |
| A call is refused because a field was sent under both its new and its former name. | After a rename, either name is accepted — but not both with different values, since Vela cannot know which one you meant. | Send the new name only. | The call is accepted. |
| Calls are refused and you are told to slow down. | Roughly one call every five seconds per connector is allowed. It protects the site you are calling as much as your account. | Spread the calls out instead of retrying immediately. | Calls are accepted again once the pace drops. |
A Toolset is unusable
| Symptom | What it means | What to do | Expected result |
|---|---|---|---|
| Your assistant sees no tools at all. | The address pasted into the assistant is wrong, or the token is missing the word in front of it. | Paste the address and token exactly as the Toolset page gives them, rather than copying the address from your browser. | The assistant lists the tools by the names you gave them. |
| The connector you want is not in Select Active Connector. | The connector is not Live, or the Toolset is read-only and this connector changes something. | Switch the connector on, or attach it to a Toolset that is not read-only if you really mean to allow that action. | The connector appears in the list and can be attached. |
| Every call is refused as if no key was sent. | The token was rotated after you pasted it, so the old one no longer works. | Press Rotate Token, then paste the new token into your assistant in the same sitting. | Calls are accepted again, and the run shows in the connector history. |
Still stuck
- Every failed run has a reference shown next to it. Quote that reference when you ask for help — it identifies the exact run, what was sent, and which version of the connector answered.
- Never repeat a call that books, sends or submits when you cannot see whether the first one landed: you would be duplicating a real booking, message or order. Read the run first, then decide.
- For anything the tables above do not cover, start from Sign a connector back in if a sign-in is involved, and Create a toolset if an assistant is involved.
What these guides prove, and what they do not
Every button name, field and result sentence in this help is checked against the screen that renders it, so a renamed control breaks that check instead of leaving you hunting for something that no longer exists. That is the limit of what is proven here, and it is worth stating plainly:
- No browser is driven when the documentation is checked: the labels below are proven present in the file that renders them, not that a live page places them where a guide says.
- Assistant-side tools (Claude, Cursor and the rest) are not exercised here. Where a guide describes what an assistant shows, that part is not verified by this repository.
- The deployed documentation version is not confirmed from this repository.
If a step here disagrees with what you see, the guide is the thing that is wrong — tell us which step, and what the screen showed instead.
What starts a repair, what it does, and where it stops.
↗Your situation doesn’t match the guide?
Talk to the team ↗