Support
Two places to ask, depending on whether the problem is with the tool or with your account.
1. Where to ask
Something wrong with the tool? Open an issue on GitHub. It is open source, the discussion is useful to the next person who hits it, and the fix arrives in a release everyone gets.
Something wrong with your account, billing, or a team? Email support@flanner.io from the address on the account. That is faster than a public issue and does not put your team's details in a search engine.
A security problem? security@flanner.io, and please read the reporting section of the Acceptable Use Policy first.
2. How long we take
Email is answered within two working days, usually sooner. Security reports are acknowledged within three working days.
There is no paid support tier and no SLA. This is a small operation, and saying so is more useful than promising an hour and missing it.
3. What to include
Three things turn most reports into a fix on the first reply:
- What you ran, and what happened instead of what you expected.
- Your version.
flanner --version, plus your operating system. - The error, in full. The last few lines are rarely the useful part.
Please do not paste plan content. It is almost never needed, and we would rather not receive it. If a specific file matters, describe its shape.
4. Things to try first
Most problems are one of a dozen known ones, and each has a command that settles it. The troubleshooting page groups them by whether the trouble is your install, your agent, or the network.
If you are opening an issue, run flanner doctor and flanner status first and paste both. Between them they cover almost everything anybody would ask you for.