Neo | DocsAsks you for help
Errors
Sometimes Neo will get stuck, and leave a comment on a ticket or pull request asking for help. You can reply with extra information, for example where to find a file that Neo needed to find.
If there is an error code, include it when Contact Support
Common scenarios:
-
When code repository / project management tool / document management tool is not setup correctly. Speak to your administrator, or see Admin and Configuration.
-
When the specification of a ticket is missing. Update the ticket and ask Neo to try again.
-
When the branch for a pull request doesn’t exist.
-
When a single code file Neo needs to edit is too large to work with.
-
When someone else pushed code to the same branch that Neo is working on.
-
No changes need to be made - for example, someone else had already pushed the changes to the branch.
-
When Neo has failed to fix CI/CD pipeline errors twice in a row, and has given up.
Caveats
Sometimes Neo can’t do something it wants to, but still has a go at finishing its main task. It will then tell you caveats to its work, such as:
-
URL you gave in a ticket that it couldn’t read
-
File it wanted to edit but couldn’t because it is binary
-
Figma document was too large to process
You may want to adjust instructions and get Neo to try again. For example, you could copy and paste the information needed from a page Neo doesn’t have permissions to read. Or change a Figma link to link to a more specific component.