Send the body below - any of 50, 80 and 100, the per cent of your allowance used, or [] for none - and, for one kind of your channels only, "channel": one of inbox, email, phone or chat.
Request body
{"points":[50,80,100]}
What to do:
Pick the points of the month's AI limit you want to hear about.
The token is proved by one read of the application.
What to do:
Xovris keeps the connection as soon as the bot's current token is sent. Do it yourself instead: reset the token on the Bot page of the Developer Portal and send the new one.
The CircleCI token is proved by one read of the project.
What to do:
Xovris reads the host's own pipelines with circleci left out, and reads CircleCI's builds the moment a personal API token that can see this project is sent. Do it yourself instead: in CircleCI, open User Settings, Personal API Tokens, make one and send it as circleci.token.
That address is not a public onehost-not-public422Xovris read what was sent, could not use it as it stood, and did not carry the request out.What to do:
Xovris reaches a Git host on the internet over https; a server inside a private network is reached through Xovris's outbound connector instead. Send its public address. Do it yourself instead: run the connector beside it.
Xovris keeps the connection as soon as a token that may read the project is sent. Do it yourself instead: make such a token in your Git host's own settings and send it here.
Missing or not right: the fields the answer names. Nothing was kept.
What to do:
PUT /v1/reviews/hosts with body 1 - or bitbucket-cloud (project workspace/repository), bitbucket-dc (base, project KEY/repository), azure-devops (base https://dev.azure.com/acme, project Project/repository); circleci body 2 and jenkins body 3 beside it.
POST /v1/systems with the body below - with "words" to name it, "description_url" where it publishes its description, and "token" (or "user" and "password") when it needs a sign-in.
PUT /v1/reviews/tracker with the body below - or linear (teamId), github (repo), gitlab (project), servicenow (base, table, user), zendesk (base, email), asana (project), azure-devops (base, project).
The Jenkins token is proved by one read of the job.
What to do:
Xovris reads the host's own pipelines with jenkins left out, and reads this job the moment a user and an API token that can read it are sent. Do it yourself instead: in Jenkins, open your user's Security page, add an API token and send it with your user name.
Xovris keeps the tracker as soon as a token that may create issues there is sent. Do it yourself instead: make such a token in the tracker's own settings and send it here.
Nothing is left to do here: the request was answered, and Xovris gives your terminal a new code by itself if it still needs one. Do it yourself instead: run the command again if you need to sign in.
Xovris opens GitHub's own page for installing the app - the repository's owner grants it there (consent: GitHub asks the owner), and this carries on once it is installed.
Xovris opens the installation's own page on GitHub where your repository is given to the app - its owner grants it there (consent: GitHub asks the owner), and this carries on once it is given.
Xovris never overwrites a secret it did not just write.
What to do:
Xovris writes it as another name instead when you press it - nothing of yours is overwritten, and your workflow reads that name. Do it yourself instead: choose another name, or delete the secret in the repository's settings first.
Someone set it again since; Xovris never deletes a secret it did not write without your press.
What to do:
Xovris deletes it when you press Delete it anyway - GitHub never shows a secret's value again, so this one delete has no undo. Do it yourself instead: delete the secret in the repository's settings if you no longer need it.
Xovris puts the domain on the build's project the moment its host is connected on Connections and the build is deployed there. Do it yourself instead: add the domain in the host's own settings.
Nothing went live: each table or field your live app holds that this change would drop, named.
What to do:
Carry on from it asking Xovris to keep everything the live app holds and add the new beside it - nothing your visitors stored is lost. Or let it replace the live data: it is kept as a checkpoint first and comes back in one step.
There is no channel to testno-alert-channel409What was asked does not fit the state things are in now, so Xovris did not carry it out.What to do:
Xovris adds your own verified email as this workspace's alert channel itself on one press - Send alerts to my email - and the test then goes there. Do it yourself instead: add your email address or connect Slack on Alerts, then send the test again.
Your repositoryand its pull request: the finding’s title (its file:line).
What to do:
Xovris files it the moment a tracker is kept: PUT /v1/reviews/tracker with its kind, where it is and a token. Do it yourself instead: copy the finding from its line in the review into your tracker.
A merged change is removed with npx xovris remove or a revert. | Nothing to close.
What to do:
Open the setup pull request first. | Xovris opens a pull request that takes the change back out itself – exactly the files it changed, each put back as it was. Do it yourself instead: run npx xovris remove in the project, or revert the merge on GitHub.
The previous new key has not sent a stored event yet, or the old key is still in use.
What to do:
Xovris places the new key through your host’s connection where it has one, and retires the old key by itself once it is quiet. Do it yourself instead: put the new key in place where your app keeps it, and Xovris still retires the old one once it is quiet.
Nothing was changed. Alerts keep going to your other channels; Xovris tries the HTTPS address again on your next press. Do it yourself instead: give the webhook a public HTTPS address.
Xovris puts the domain on the build through your own Vercel, Netlify or Cloudflare Pages connection instead - send the same request with "via" naming it, and that host issues the certificate; Xovris's own door turns on the moment this environment holds it. Do it yourself instead: add the domain in your host's own settings.
Xovris hosts it here once this environment has its site key, and deploys it to your Vercel, Netlify or Cloudflare Pages the moment one is connected. Do it yourself instead: take the files from the job and put them on any host.
This Xovris has no push key configured, so a device cannot subscribe.
What to do:
Xovris keeps every alert going to your email meanwhile - one press on Send alerts to my email if it is not on yet - and push turns on here without anything for you to do. Do it yourself instead: connect Slack on Alerts.
The access token still authenticates after it was revoked, or the refresh token still mints new access tokens. Xovris revoked it several times.
What to do:
Xovris keeps the connection listed as not removed and revokes again on your next press. Do it yourself instead: remove the app in Slack under Manage apps.
Xovris keeps the connection the moment its sealed store is back; send this again then. Do it yourself instead: ask Xovris in Slack, Teams or by email meanwhile.
Xovris reads your projects from Vercel again itself and links each one it is given – nothing was left half written. Do it yourself instead: open the integration in Vercel and choose the projects again.
Xovris opens this page with the code already filled in from your terminal, and your terminal asks for a new code by itself when one expires. Do it yourself instead: check the code in your terminal, or run the command again for a new one.
Nothing was read from your repository and nothing was changed.
What to do:
Xovris opens the change as a pull request the moment its GitHub App is switched on here. Do it yourself instead: the step's own words name the file and the change.
No push subscription with that address is on in this workspace.
What to do:
Nothing to turn off. Xovris turns push on here the moment you allow notifications from this browser on Alerts - that permission is your own, so only you can give it.
It may have been removed, or belong to another Xovris workspace.
What to do:
Xovris connects Slack again with your one approval on Slack's own page (GET /v1/integrations/slack/install), reads the token back and sends a test. Do it yourself instead: open Alerts and press Connect Slack.
Xovris links it by itself the moment Vercel tells it the project was added. Do it yourself instead: open the integration in Vercel and add the project there.
Xovris links it again itself while Vercel still gives the integration this project, and lists every project it links. Do it yourself instead: open the integration in Vercel to see its projects.
Your terminal asks Xovris for a new code by itself and opens it here - nothing to run again. Do it yourself instead: run the command again in your terminal for a new code.
Xovris makes this token and writes it into the repository itself wherever its token maker is on; on this server it is not on yet, and nothing was written. Do it yourself instead: create the token under Settings, Developers and add it to the repository yourself.
Each one with its status, what happened and the step that gets you going again. Press one for every case it covers.
When Xovris answers a request with a problem, its type is a link to this list. Each one says what happened and what to do next, in the words the answer itself uses.
Still stuck?
The status page says whether Xovris knows of a wider fault. Support can look at your case: send the answer you got and what you were doing.