Troubleshooting

Start with Logs

1. Open Logs. It opens at the bottom on most tabs and on the right on the Table Discovery tab.
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.

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.
• SSO profiles are included in the trial and in Professional and Enterprise.
• For AWS Login profiles, select Sign in with browser. If the browser does not return to Dynomate, select Use a code instead.
• 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. The profile needs sts:GetCallerIdentity.

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: sts:GetCallerIdentity, dynamodb:ListTables, and dynamodb:DescribeTable.
• Table reads: dynamodb:Query or dynamodb:Scan.
• Edits: dynamodb:TransactWriteItems for staged commits, and dynamodb:UpdateItem for the Edit Item dialog.
• Imports: dynamodb:BatchWriteItem in overwrite mode, dynamodb:PutItem in skip mode, and s3:GetObject for an S3 source.
• Truncate: dynamodb:Scan and dynamodb:BatchWriteItem.
• Athena queries: the Athena query actions, and access to the data source and the S3 result location.
• Amazon Aurora DSQL access: dsql:ListClusters and dsql:GetCluster for discovery, and dsql:DbConnect or dsql:DbConnectAdmin to connect.

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.
• In a request, plain HTTP works only with localhost, 127.0.0.1, or ::1. See Endpoints.

Failed Scan or Query

• For Query, confirm the selected index, if any, 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.

Staged change failures

• A commit can contain at most 100 transaction actions, and an update that changes a key uses two. Commit fewer changes at a time.
• DynamoDB item size, key, condition, and transaction rules still apply.

See Transaction limits.

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 table can run one import at a time, and not during a truncate. See Restrictions.
• 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.

Truncate failures

• A cancelled or failed truncate can leave some items in the table. Deleted items stay deleted. See Monitor or cancel.
• Items that an application writes during the job can remain. Stop producers first, and verify the table after the job. See Concurrent writes.
• A truncate cannot start while an import or another truncate runs on the same table.

SQL snapshot failures

• A new snapshot performs a full-table scan. Confirm read permission and available read capacity.
• Keep free disk space above the table size estimate. See Plan local storage.
• 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. See Query with DuckDB SQL.

Athena failures

• Confirm the profile, Region, catalog, database, and table in the discovery results.
• 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.

Aurora DSQL failures

• If a Region shows "Clusters not listed", add the cluster by ARN.
• To find the step that fails, run the connection test.
• If Aurora DSQL refuses the connection with 28000, check the IAM action, the role and its mapping.
• If the token is expired or not yet valid, check the clock of this computer.
• If you signed in again, run the statement again or select Refresh. Aurora DSQL tabs do not reload.
• If Dynomate cannot reach the cluster, check the route, DNS and port 5432.
• If the certificate does not verify, check the TLS settings of the cluster.
• If a statement fails with OC000 or OC001, run it again.
• If Dynomate shows Outcome unknown, check the data before you run again.
• If an error names an Aurora DSQL limit, read the fix for that Aurora DSQL limit.

Request run failures

• If a check fails before the run, select each diagnostic in the results panel to go to its field. See Problems before a run.
• Look up the code in Error codes.
• If a request file shows a diagnostic in the collection, select Reveal file, correct the file, then select Refresh collections. See Invalid files.
• If a legacy collection does not migrate, see migration errors and conflicts.

CLI failures

• For install problems, see CLI installation troubleshooting.
• If AWS credentials fail, sign in with the app or the AWS CLI first. The CLI does not sign in for you. See AWS credentials.
• If validation fails, the CLI shows only the first diagnostic. See errors in the CLI and CLI loading codes.
• If every requests run fails with APP_DATA_SCHEMA_UNSUPPORTED, update the CLI.

Trial and license status

• After a purchase or seat change, select Refresh status in the License dialog.
• If all seats are in use, ask the subscription owner to free or reassign a seat.
• If Dynomate cannot verify access online for seven days, it uses Community access until a check succeeds. Connect to the internet and select Refresh status.

See License activation and Access verification.

App 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 to apply the update.
• The downloaded update is not active until Dynomate relaunches.
• If updates keep failing, reinstall from the download page.