Common Causes and Solutions:
1. GroundPlex Configuration Differences
The most likely cause is differences in GroundPlex configurations between the environments:
JVM Settings: Different heap memory allocations or JVM parameters
Node Resources: Varying CPU, memory, or disk space availability
Network Configuration: Different proxy settings, firewall rules, or network latency
SnapLogic Version: Different SnapLogic runtime versions between GroundPlex instances
2. Account and Authentication Issues
Account Configuration: Verify that the same account is being used on both GroundPlex instances
Permissions: Check if the GroundPlex has proper permissions to execute preview operations
Authentication: Ensure authentication credentials are properly configured
3. Preview Data Execution Settings
Check the Snap Execution setting in your JSON Generator:
Ensure it's set to "Validate & Execute" (not "Execute only")
"Execute only" mode disables preview data generation during validation
4. GroundPlex-Specific Limitations
Some GroundPlex environments may have:
Resource constraints that prevent preview execution
Security policies that restrict certain operations
Custom configurations that affect Snap behavior
5. Debugging Steps
- 1.
Compare GroundPlex Settings:
Check the GroundPlex configuration in both environments
Compare JVM settings, memory allocation, and node configurations
- 2.
Verify Snap Configuration:
Ensure the JSON Generator has identical settings in both environments
Check the "Snap execution" dropdown is set to "Validate & Execute"
Review the GroundPlex logs for any errors or warnings during preview execution
Look for memory issues, timeout errors, or permission problems
- 4.
Test with Simple Pipeline:
Create a minimal pipeline with just the JSON Generator
Test preview functionality to isolate the issue
Monitor CPU, memory, and disk usage during preview attempts
Check if the GroundPlex is under resource pressure
6. Immediate Workarounds
Use Cloud Execution: Temporarily run the pipeline on the cloud to verify functionality
Full Execution: Use "Execute only" mode and check the actual pipeline output
Alternative Testing: Use a different Snap type to test preview functionality
