Troubleshooting & release limits

Sign-in and workspace access

401: sign in again; expired or revoked sessions cannot be reused. 403: check workspace membership/role and selected hostname. 409 during setup: complete onboarding. If a team link returns 410, ask the administrator for a fresh invitation. If a chosen subdomain is not reachable, use the central application while wildcard routing is pending. There is no automated password recovery in this release.

Conflicts and invalid input

409 on a record/list/dashboard/member means data changed or is unavailable. Refresh, review current values and reapply the intended edit. Do not silently remove version checks. 400 means an invalid field, relation, state transition, CSV row or provider configuration; correct the message before saving. A valid preview can become stale before commit/launch.

Billing and provider failures

402 means an active plan is needed; the owner manages Billing. 429 means a rate limit: wait for the indicated window and reduce requests. Provider errors may be 502/503. Check authorization, connection choices and current provider status. An Unknown outreach outcome may already have been accepted: inspect the provider before creating a new campaign/attempt. Cancelling cannot recall a message or call already accepted.

What this release does not include

The current release covers the documented modules and APIs; the full PRD is still in progress. Not implemented: customer custom domains, full marketing/social modules, mixed-channel outreach, audiences above 500 per launch, automatic invoice email/customer collection/bank reconciliation, arbitrary SQL/formula dashboards, MFA/recovery/login OAuth, granular permission policies, ownership transfer and suppression removal.

Scalability depends on workload and deployment capacity. JSON field filters currently scan the selected object; large-data indexes, queue throughput tuning, monitoring/recovery drills and a key-rotation migration remain operational work. The product is responsive and configurable within documented limits; no unlimited scalability or 100% customization guarantee is implied.

Get help with useful context

Contact support@drykraft.com with the page, action, time and X-Request-ID if available. Include the recovery message and a redacted screenshot. Do not share account passwords, provider secrets, invitation/hook tokens, session cookies or customer data unnecessarily.