Troubleshooting
Where to find what a pmo message means and what to do about it, by when it happened.
pmo never fails silently. Every refusal names what it wants, changes nothing, and ends with an exit code that says what kind of problem it was. Read the message first; it is written to be acted on.
Find your message
| When it happened | Where the messages are explained |
|---|---|
| Installing on Windows | Installing on Windows → When something goes wrong |
| Installing on a Mac or Linux | Installing on a Mac or Linux → When something goes wrong |
Signing in with pmo login | Signing in → When it does not work |
| Using a key | Your key → When the key stops working |
| Any command, first time on this computer | How it works → When something goes wrong |
| Working on tasks | Everyday work → When something goes wrong |
By exit code
| Code | Usually means | First thing to try |
|---|---|---|
| 1 | Nothing matched | Not an error. Drop a filter, or there is simply nothing open for you. |
| 2 | A typo in the command | Run pmo help <command> and compare. |
| 3 | Not found | Check the short name. If a colleague can see it, ask the PMO owner for access. |
| 4 | Someone changed it first | Show the record again, then repeat your change if it still applies. |
| 5 | A rule said no | The message names the rule and who can do it instead. |
| 7 | The server was busy | Try again; nothing was written. |
| 8 | Not signed in | Run pmo login, or put a key in your settings file. |
| 9 | pmo itself failed | Tell the PMO owner, with the command you ran. |
Still stuck? Send the PMO owner the command you ran, the full message, and the output of pmo whoami.