When something does not work
Almost everything that goes wrong in Cyber Corp is one of five things, and each one has a fix you can do yourself in a couple of minutes. Start with the diagram, then read only the section it points at.
Start with what you saw
You do not need to know what broke. You only need to know what the screen said. Match it against the five branches below, go to that section, and ignore the rest of this page.
A task was refused because the month ran out
If your copilot comes back saying you have reached your monthly limit, nothing is broken. Every plan includes a number of tasks a month. One task uses one of them, and once they are gone the next task is refused instead of run.
| Plan | Tasks a month | Saved automations | Automations running at once |
|---|---|---|---|
| Free | 500 | 5 | 1 |
| Pro, $20 a month | 5000 | 100 | 25 |
| Max, $100 a month | 25000 | 500 | 125 |
The count goes back to zero on the 1st of the month, and there is no daily limit on top of it. So one answer is simply to wait. On the 1st you have the whole allowance again, and nothing else about your account changes in the meantime: your conversations, your connected apps and your automations all stay exactly where they are.
Open Settings, then Billing
Under Usage, the Operations bar shows how much of the month you have spent. That is the number the refusal is about.
Choose an upgrade under Compare all plans
Choose an available plan in Billing and read its price and billing period. A first subscription goes through consent and the secure payment page. An upgrade to an active subscription asks for confirmation and updates the existing subscription.
Ask for the task again
The new ceiling applies at once. Select Retry under the refused message, or simply say it again.
You cannot get back in
Two very different things keep you out, and they look nothing alike. If no email arrived, start at the top. If the page says there have been too many attempts, go to the lock at the bottom.
The email that never left
Sometimes the email genuinely did not go out, and Cyber Corp says so instead of pretending. The screen after sign-up then tells you the account is created and gives the reason, rather than asking you to check your inbox. Your account does exist. Use the Resend the email button underneath, which in that case is ready straight away.
The email that arrived somewhere you did not look
Check the spam or junk folder first, and search for the words Cyber Corp rather than scrolling. Give it about five minutes before you decide it is missing, and check the address you typed. If you have already left the sign-up screen, go to the sign-in page and try to sign in: while the account is not yet activated, a Resend email link appears on the right of the Username / Email line.
Both kinds of link run out. An expired or already-used link is not a loss, and it does not mean the account is damaged. Ask for a fresh one.
- Activation link
- 24 hours, and it works once
- Password reset link
- One hour, and it works once
- Between two emails
- Sixty seconds, counted down beside the sign-up resend button
- Activation emails per account
- Five, then no more are sent
- Reset emails per account
- Five, counted separately
Ten wrong passwords in a row
Ten wrong passwords on the same account lock it for fifteen minutes. While it is locked, sign-in is refused even when the password is right, which is the part that throws people: you can finally remember it on the eleventh try and still be turned away. The message tells you there have been too many failed attempts, but not how long it lasts, so here it is.
Waiting it out is enough, and nothing else about the account has changed. If you would rather not wait, or if you are locked out because you genuinely cannot remember the password, go through a password reset instead. That clears the lock the moment your new password is saved, because the emailed link has already proved the mailbox is yours.
A connected app that stopped working
Open Settings, then Connections. The row for the app reads Connected or Not connected. Connected means your details are stored, not that they still work. Nothing tests them in advance: they are tried at the moment a task needs them, which is why an app can go from fine to broken with nothing at all changing on this page.
The cause is almost always the credential itself. A token that expired, a key you regenerated in the other app, a webhook address for a channel that no longer exists. So the fix is to replace it, not to reconnect everything.
Check what is stored
Find the app in Settings → Connections and open its form. Connected means every required field is stored; it does not certify a successful request. The row has no last-success date.
Fetch fresh details from that app
The small link under the row's form says exactly where they live, for example the page where a webhook or an API key is created.
Select Manage and fill in what changed
You only need the box that broke. A box you leave blank keeps the value already stored, so a connection with three fields does not lose the other two because you pasted one new secret.
Select Update, then try a task
After saving, ask Copilot for a small supported operation or run the relevant workflow step. Connections has no Test connection control. Read the task’s response for missing permissions, expired credentials or other errors.
If it still fails, start over
Remove the connection with the bin button beside Update, then set it up again from scratch. That clears anything left over from an older set of fields.
One thing to expect: a task that was already running when you saved carries on with the details it started with. Judge the result on the next run rather than on the one that was in flight.
An automation that will not run
A workflow only starts on its own if it is on a schedule. Open it, select the alarm button in the run controls and look at Scheduled routine: while the routine is on it carries an ACTIVE badge, and once it has run at least once it shows the time of that last run. No badge means no schedule, and nothing was ever going to start it.
For scheduled or cloud runs, open Notifications to find completion or error messages and their workflow links. Runs shows the browser editor’s recorded runs, not a combined cloud history. The scheduling panel’s last-run time marks an attempted trigger, not proof of success.
| State | What it means | What to do |
|---|---|---|
| Running | The browser run started and has not finished. | Watch its steps, or use Pause and Stop. If the tab was closed, look for Interrupted when you return. |
| Completed | Every step finished | If the result was wrong, open the run and read what each step returned. |
| Failed | A step stopped the run | Open it and read the message on the step that stopped. |
| Cancelled | Somebody stopped it by hand | Start it again when you are ready. |
| Interrupted | The browser closed or refreshed before the run finished. | Return to the Runs tab and start another run when ready. |
| No scheduled result | The allowance may be exhausted or this workflow may still be busy. | Check Billing, Notifications and the last trigger time before changing the workflow. |
| No browser history | This editor has no recorded browser runs; this does not rule out a cloud run. | Run it manually to inspect the steps, or check Notifications for cloud and scheduled results. |
A completed scheduled run leaves a notification; a failed one is marked as an error and links back to the workflow. The browser Runs and Activity panels describe browser-recorded runs. They do not currently provide the full scheduled-run history.
When none of this fits
First check whether the problem is ours. The System status link at the foot of any page opens the status page. It runs its checks live from your browser, marks each one Operational or Unreachable, and re-checks every thirty seconds. There is a Re-run checks button if you do not want to wait.
If a check is unreachable, retry and check your connection too. Passing all three only confirms those endpoints: it does not test every task, connected app or backend. If the issue persists, send its exact message and time to support.
Write to support@cybercorp.ai
Explain the issue and include the exact message, page and approximate time.
Say what you asked for and what happened instead
The exact words you used matter more than a description of them, and roughly when it happened is enough. No screenshot is required.
Include the code in brackets
If a message came back with five characters in brackets, such as (hjhjx), copy them in. They point at the exact place the request stopped.
Read next