DynamoDB Local missing tables after commit

This issue could be related to a few common causes when working with DynamoDB Local in NoSQL Workbench.

First, check if there might be a propagation delay. While DynamoDB write operations typically propagate within 1 second, large tables with many items or multiple Global Secondary Indexes (GSIs) can cause propagation latency.

Another possibility is that the tables might be in a "CREATING" state rather than "ACTIVE" state. DynamoDB operations will fail with a ResourceNotFoundException if you try to access tables that aren't yet in the ACTIVE state.

Since you're using NoSQL Workbench with DynamoDB Local on macOS, there could also be an issue with the Java Runtime Environment. NoSQL Workbench requires JRE version 11.x or newer to run DynamoDB Local properly. If your JRE isn't properly configured or detected, it might cause inconsistent behavior.

To troubleshoot:

1. Try refreshing your connection or restarting NoSQL Workbench
2. Verify that all tables are in the ACTIVE state
3. Check that your JRE is properly installed and configured
4. Try recreating the missing tables individually through the Operation Builder
5. If possible, export your data model and try committing it again

If the issue persists, you might need to manually check if the tables exist by using the AWS CLI with your local endpoint to list all tables and verify their status.
Sources
Troubleshoot missing table items in GSI | AWS re:Post
Troubleshoot "ResourceNotFoundException" error in DynamoDB | AWS re:Post
[macOS] NoSQL Workbench DynamoDB Local unable to start via GUI on/off switch because it cannot find an SDKMAN-managed JDK | AWS re:Post