Status and support

Ask a question

• The community forum: GitHub Discussions in voplica/help, for questions and ideas. It is public: search first, and never post a key there — see what never to post.
• Direct support: the Support page in the studio, private and answered by the Voplica team. With a Base or Premium plan, any question about your account or a run; without a plan, up to three open issues about billing, legal notices, security vulnerabilities and bugs. SUPPORT.md has the details.

Report a bug

The fastest route is a Bug report issue on the studio’s Support page, which is private. GitHub Issues in voplica/help take bug reports too; they are public and may be slower.

Report a security vulnerability

Never in public: not in an issue, a discussion or a pull request. The fastest route is a Security vulnerability issue on the studio’s Support page; you can also e-mail security@voplica.com, or use Report a vulnerability on voplica/help’s Security tab. The API is in scope; SECURITY.md has the rules.

What to include about an API call

• the method you called, as its path (/voplica.api.payment.PaymentService/GetBillingInfo);
• when you called it, the HTTP status, and the answer’s code and message;
• for a run, the run’s id (workflowExecutionId).

Caution

Never send your API key, in a support issue or anywhere else. If you posted it somewhere by mistake, revoke it at once on the API keys page.

Status

There is no status page yet. A temporary failure answers 503; retry it, and report it if it lasts.