Dynomate

Troubleshooting

Confirm the active tab, AWS profile, Region, and resource first. Then use Logs to read the service, operation, error code, request ID, and failure message.

Start with Logs

  1. Open Logs from the bottom or right dock.
  2. Return to the tab that failed. Logs follows the active table or SQL source.
  3. Expand the failed row.
  4. Copy the SQL, DynamoDB parameters, or sanitized activity record if you need to report the issue.
  5. Record the AWS request ID before you clear activity.

See Logs for scope, retry, download, clear, and retention behavior.

Authentication failures

  • For SSO, select the profile status and complete sign-in in the browser. Return to Dynomate after the browser reports success.
  • For an expired SSO session, refresh the profile or run aws sso login --profile PROFILE_NAME, then load tables again.
  • For access keys, confirm that the profile has a valid access key and secret key in the standard AWS files.
  • For MFA profiles, enter the current six-digit code when Dynomate requests it.
  • Check the STS activity row if Dynomate cannot resolve the account identity.

Wrong profile or Region

  1. Open table discovery.
  2. Confirm the profile name and the account identity shown for that profile.
  3. Select the Region that contains the resource.
  4. Load tables again and open the table from the new result.

A table tab keeps the profile and table ARN that were used when the tab was opened. Open a new tab after you change discovery context.

Permission errors

Read the AWS error code in Logs. An AccessDenied error means the current principal cannot call the displayed service operation on the displayed resource. Ask an AWS administrator for the smallest policy that covers the required action. Discovery commonly needs list and describe permissions. Table reads need Query or Scan. Writes need the matching Put, Update, Delete, or BatchWrite permission. S3 imports and Athena queries also need access to their S3 locations.

DynamoDB Local and LocalStack

  • Set endpoint_url in the selected AWS profile.
  • Use http://localhost:8000 for a default DynamoDB Local process or http://localhost:4566 for a default LocalStack process.
  • Confirm that the process is running and that its port is reachable from the desktop app.
  • Use non-empty placeholder credentials. The AWS SDK requires them even when the local service does not validate them.
  • If Dynomate treats the profile as AWS instead of local, use localhost, 127.0.0.1, or ::1 in the endpoint host.

Failed Scan or Query

  • For Query, confirm the selected base table or index and enter the correct partition key type and value.
  • Check each filter path, operator, and value type.
  • Expand the log row to inspect the parameters that Dynomate sent.
  • Select Run on a logged Query only when the matching table tab is active. Scan rows do not have this retry action.
  • If loading the next page fails, stop scrolling, read Logs, then scroll again after the failed load has ended.

Import and export failures

  • Use import preflight. Fix every blocking issue before you start the job.
  • For JSON, provide an array of items. For CSV, confirm the detected format and column names.
  • For S3, confirm the object ARN, bucket Region, format, profile, and s3:GetObject permission.
  • For table-to-table import, confirm both profiles, source table, destination table, and conflict mode.
  • A current-page download requires loaded rows. A selected-row download requires at least one selected row.
  • For a full export, read the job error in the table or SQL tab. Start a new export after the failed job ends.

SQL snapshot failures

  • A new snapshot performs a full-table scan. Confirm read permission and available read capacity.
  • Wait until the snapshot artifact status is ready before you run SQL.
  • If the status is failed, read the export or artifact error and create a new snapshot after you fix the cause.
  • If the snapshot is marked missing, its local artifact is no longer available. Create a new snapshot.
  • Use snapshot for the current snapshot and history only when you need the combined snapshot history.

Athena failures

  • Confirm the profile, Region, catalog, database, and table.
  • Open query settings and select an enabled SQL workgroup.
  • If the workgroup does not set an output location, enter an S3 output URI that the principal can use.
  • Check Athena and S3 permissions in Logs.
  • Dynomate stops a query that exceeds its ten-minute polling limit. Reduce the query scope or run it again after you resolve the cause.

Update failures

  • Select Try Again to return to the update prompt after a download error.
  • If the download fails again, close Dynomate, check the network connection, then relaunch the app so it can check for the update again.
  • If Restart Now fails, close and reopen Dynomate manually.
  • The downloaded update is not active until Dynomate relaunches.
Previous App updates