Skip to main content
Get help with common issues and find solutions to problems you might encounter when using Orka.

​
Source connection

Common causes:
IssueSolution
Incorrect credentialsVerify username/password or service account
Network connectivityCheck firewall rules and network access
Wrong host/portVerify the hostname and port number
Database name typoConfirm the exact database name
Insufficient permissionsEnsure the user has required database permissions
Verify credentials outside of Orka first (for example, using a database client).

​
Destination connection

Common causes:
IssueSolution
Invalid credentialsVerify your personal access token or service account credentials
Incorrect workspace URLCheck the URL format and ensure it’s correct
Insufficient permissionsEnsure the account has required write permissions
Network connectivityCheck firewall rules and network access
Expired tokenGenerate a new personal access token
Test credentials outside of Orka first using the destination’s native tools.

​
Data catalog

Possible causes:
  • The database contains no tables
  • The user lacks permission to list tables
  • Tables are in a different schema or catalog
  • Active filters hide all tables
To fix:
  1. Verify the database has tables with a database client
  2. Check the user has SELECT and SHOW TABLES permissions
  3. Try to adjust table filters (show empty tables)
  4. Verify you connected to the correct database/schema
Slow table discovery can be caused by:
  • Large number of tables in the database
  • Slow database response
  • Network latency
Slow data scan can be caused by:
  • Large tables
  • Many tables selected for scan
  • Complex data protection rules
  • Database load
To improve performance:
  • Use filters to limit scope (hide empty, test, backup tables)
  • Scan tables in smaller batches
  • Schedule scans in off-peak hours
  • Start with smaller tables to test the workflow
This happens when data protection rules are too broad and match more fields than you need.To fix:
  1. Review which data protection rules match
  2. Check if prebuilt rules need adjustment
  3. Members of the Data protection admin group should review and adjust rule patterns
  4. Consider custom rules with more specific patterns
Test rule patterns with sample data before you scan large databases to find overly broad patterns.
Once you publish tables to the catalog, you can’t unpublish them. Published tables may have active pipelines that depend on them.If you need to remove tables:
  1. Delete any active pipelines that use the tables
  2. Contact a member of the Admin group to discuss removing the tables from the catalog
Consider carefully which tables to publish before you complete the publish workflow.

​
Data protection rules

Common causes:
  • Rule action set to None - rule matches but takes no action
  • Pattern does not match - regular expression does not match your data
  • Rule priority - another rule with higher priority applies instead
  • Rule not saved - changes were not saved
To fix:
  1. Use the pattern testing interface with sample data
  2. Verify the action is set (not None)
  3. Test the regular expression pattern
  4. Check for conflicting rules with higher priority
  5. Re-save the rule if needed

​
Pipelines

If you delete a destination that’s being used in an active pipeline, the pipeline will break.To fix:
  • Recreate the deleted destination with the same configuration, or
  • Create a new pipeline with a different destination
Always check for active pipelines before you delete a destination.
This is usually caused by insufficient permissions.To fix:
  1. Verify the service account or user has write permissions.
  2. Check the target schema or data exists.
  3. Verify there’s sufficient storage capacity.
  4. Make sure to Test connection.