Signing in#
“You have no account here”#
You signed in to Microsoft, and there is no Eido Build user with your email address. Ask an admin to add you in Admin → Users. See Users and permissions.
I cannot see a project#
You have not been given it. An admin gives each person their projects in Admin → Users.
One screen, and nothing else works#
Eido Build is locked. The screen says why and shows your install id. See Licensing.
Work that does not start#
I approved something and nothing happened#
It is queued. One of these is true:
- its release is still planned. It starts when the release is opened.
- the project starts work manually. Somebody needs to press Start.
See Planning releases.
No agent stage will start, anywhere#
The month’s budget for agents has been spent. An admin can raise it in Admin → Workbenches. See Costs and budgets.
A stage has been queued for a long time#
A stage before it has not finished, or is waiting for approval. Open the work item to see which stage has it and who it is waiting on.
Stages#
A stage stopped part way#
It reached its spend cap. An admin or project admin can raise the cap on the work item, and the stage carries on from where it stopped. See Working with an agent stage.
A stage says it is waiting on something outside#
It is waiting for a deployment to finish. It checks once a minute, and carries on when the deployment is ready, has failed or has taken too long. Replying to the stage cancels the wait.
A work item shows a merge conflict#
The project’s default branch could not be merged into the work item’s branch cleanly. The next coding stage is told and resolves it.
The pull request is not merging#
The merge stage shows what it is waiting for. Usually the pull request needs an approval on your repository host, or changes have been requested.
The second merge has nothing to merge#
GitHub deleted the branch after the first merge. Turn off Automatically delete head branches on the repository. See GitHub.
Releases#
Release now is refused#
The release’s page lists why. Every finding must be decided, everything in the release must be finished, and no check can still be running. See Cutting a release.
I cannot open a release#
Another release is already in progress. Only one can be, apart from a hotfix.
I cannot put a work item in a release#
The release is being cut. A frozen release takes nothing new except a fix for something its checks found.
Agents#
An agent did not run#
Open the agent’s page. A run that did not start is recorded as skipped, with the reason, most often that it would have gone over the agent’s daily cap.
Remember that schedules are in UTC.
An agent’s suggestion never appeared#
It may have been dropped as a repeat of work that is already open. The run’s log says what it matched.
Notifications and email#
I am not getting browser notifications#
They only arrive while Eido Build is open in a tab. Check also that you allowed notifications for the site in your browser, and that you have them turned on under your name in Eido Build.
Emails are not arriving#
An admin should press Send a test email on the SendGrid tile. See Email.
Notification emails have no button#
This Eido Build’s address has not been set on the SendGrid tile.
Connections#
A project’s repository cannot be reached#
On GitHub, the Eido app is probably not installed on that repository. See GitHub. On Azure DevOps, press Check on the Azure DevOps panel. See Azure DevOps.
Admin warns that it has not checked in#
Eido Build cannot reach license.eido.io. Check outbound access. After 14 days without a check-in it locks. See Licensing.
Windows 365#
See the table at the end of Windows 365.