Scylla

Support

Troubleshoot Scylla

Identify the failing layer and retry the smallest task that reproduces it.

Record your Scylla build and version, then identify whether the failure concerns launch, account access, provider authentication, project scope, policy, credentials, Memory, or an external service. Change one relevant setting at a time.

Checks by symptom

Symptom Check first
Scylla will not launch Build requirements, installation, Windows identity, endpoint-security messages
Provider connects but work does not run Mode, active project, effective policy, required capability
Files or references are unavailable Workspace or Knowledge Scope and folder permissions
SSH or database operation fails Connection, protected reference, network, and remote permissions
Git action is refused Effective Git policy and remote-host permissions
Memory appears missing Project binding, source, availability, organization account
Team features are missing Membership, assigned seat, entitlement refresh, enabled service
Unexpected outbound context appears Payload details, selected project, reference scope; stop the job if needed
Tool update fails Tool identity/version, supported action, permissions, sanitized error

Avoid deleting local Memory or resetting all configuration as an initial response to a service failure.