Data Browser App
Troubleshooting
Troubleshooting
This guide covers common issues you may encounter when using the Data Browser App and how to resolve them.
Common Issues
Issue: Collections Not Loading
Symptoms:
- Sidebar shows empty or loading state indefinitely
- "No collections found" message appears
- Error message in the sidebar area
Cause: Usually caused by database initialization issues or connection problems.
Solution:
- Refresh the page to reinitialize the database connection
- Check browser console for RxDB errors
- Verify you're logged into the correct organization/workspace
- Ensure the RxDB database has been properly initialized
- If using REST mode, verify the server is running and accessible
Issue: Data Table Shows Empty
Symptoms:
- Collection selected but no data appears
- Empty state message shown
- Pagination shows 0 results
Cause: May be caused by filters, no data in collection, or query errors.
Solution:
- Clear all filters using the "Clear Filters" button
- Verify the collection actually contains documents
- Check if filters are too restrictive
- In REST mode, verify server connection is working
- Try switching to Local mode to compare results
Issue: Cannot Edit Cells
Symptoms:
- Clicking on cells doesn't activate edit mode
- Cell appears non-editable
- No cursor change on hover
Cause: The cell may contain a system field or the field type doesn't support inline editing.
Solution:
- System fields (
id,createdAt,updatedAt,_deleted,_rev) are read-only by design - Complex objects and arrays open in a content modal instead of inline editing
- Try using the edit button to open the full document form
- Check if you have write permissions for the collection
Issue: Filter Queries Return Wrong Results
Symptoms:
- Filter applied but unexpected results appear
- More or fewer results than expected
- Filter seems to have no effect
Cause: Operator selection, value format, or field type mismatch.
Solution:
- Verify the operator matches your intent:
- Use
equalsfor exact matches - Use
containsfor partial text matches (case-sensitive) - Use
exists/notExistsfor checking field presence
- Use
- Ensure value format matches field type:
- Strings: Use text as-is
- Numbers: Enter numeric values only
- Booleans: Select from dropdown
- Enums: Select from provided options
- Remember that filters are AND-combined (all conditions must match)
- Clear filters and re-add them one at a time to identify the issue
Issue: REST Mode Connection Failed
Symptoms:
- Error message when switching to REST mode
- "Connection refused" or timeout errors
- Collections don't load in REST mode
Cause: RxDB Server may not be running or misconfigured.
Solution:
Verify RxDB Server is running:
yarn docker:logs # Check server statusConfirm server URL is correct in server configuration
Verify authentication token is valid and not expired
Check that Domain ID matches server configuration
Ensure no firewall is blocking the connection
Try accessing the server URL directly in browser to verify it responds
Issue: Document Save Fails
Symptoms:
- Inline edit doesn't persist
- Form submission shows error
- Document appears to save but reverts
Cause: Validation errors, schema violations, or connection issues.
Solution:
- Check for validation error messages in the form
- Ensure required fields are filled in
- Verify field values match expected types:
- Enum fields must use allowed values
- Reference fields must contain valid IDs
- Check browser console for detailed error messages
- In REST mode, verify server connection is stable
- Try refreshing the page and re-editing
Issue: Cannot Delete Documents
Symptoms:
- Delete button doesn't respond
- Confirmation dialog appears but document remains
- Batch delete fails silently
Cause: Permission issues, soft delete, or connection problems.
Solution:
- Verify you have delete permissions for the collection
- Note that FlowState uses soft delete - documents may appear removed but exist with
_deleted: true - Check browser console for error messages
- Refresh the page and verify deletion status
- In REST mode, ensure server connection is active
Issue: Pagination Not Working
Symptoms:
- Page controls don't change displayed data
- Same data appears on all pages
- Page size selector has no effect
Cause: Usually a client-side state issue or data loading problem.
Solution:
- Refresh the page to reset pagination state
- Check if filters are affecting total result count
- Verify data exists beyond the first page
- In REST mode, pagination relies on server support - verify server is processing skip/limit
Issue: Document Form Shows Wrong Fields
Symptoms:
- Form fields don't match expected schema
- Missing required fields
- Extra unexpected fields appear
Cause: Schema mismatch or caching issues.
Solution:
- Refresh the page to reload schemas
- Verify you're viewing the correct collection
- Check that schema definitions are up to date in the codebase
- Clear browser cache if schema recently changed
Performance Issues
Issue: Large Collections Load Slowly
Symptoms:
- Long loading time when selecting collections
- Browser becomes unresponsive
- High memory usage
Cause: Large data sets being loaded into memory.
Solution:
- Use pagination - avoid loading more than 100 rows at once
- Apply filters to narrow down the data set before loading
- Use REST mode for large collections (server-side pagination)
- Consider using the CLI or MCP tools for bulk data operations
Issue: Inline Editing Feels Sluggish
Symptoms:
- Delay between clicking and edit mode activating
- Typing in edit mode lags
- Saving takes a long time
Cause: Table re-rendering or database write performance.
Solution:
- Reduce page size to minimize re-rendering
- Close other FlowState apps to free resources
- Check if RxDB replication is syncing large amounts of data
- Use the document form modal for editing multiple fields at once
Getting Help
If you can't resolve your issue:
- Check the FAQ for additional answers
- Review the Features documentation for proper usage
- Contact support with:
- Description of the issue
- Steps to reproduce
- Screenshots if applicable
- Browser and device information
- Connection mode (Local or REST)
- Collection name and approximate document count
- Any error messages from the browser console