ReferenceGet Help
Get Help
Where to send a problem, a question about Credible, a Malloy question or a security report, and what to include so a failed query, publish, build, connection or CLI command can be investigated
Pick the channel that fits what you need:
Support
Something isn't working: email support@credibledata.com
Questions about Credible
Trying it out, plans, Enterprise features or private networking: email hello@credibledata.com
Malloy Community
Ask about the Malloy language in the Malloy Slack
Security
Report a vulnerability: email security@credibledata.com
Before You Write
- Check the Troubleshooting table on the page for the feature you're using. Many how-to and connection pages have one, listing common errors with their cause and fix.
- Ask the agent in the Credible App. It searches these docs, so it can point you to the right page or setting.
What to Include
| Kind of issue | What to send |
|---|---|
| Any issue | Your organization name, the environment and package involved, what you did, the exact error text, and roughly when it happened, with your time zone |
| A query or a publish | The package version |
| A failed build | The package, version and run ID (cred ls run <package> lists runs) |
| A connection | The connection name and database type |
| The CLI | The output of cred -V, and the command's output run again with --debug, with any tokens removed |
| CI/CD | The URL of the failed GitHub Actions run |
Never send passwords or keys, including API keys and the contents of a connection file.