Hi Rachel - Search results don't reveal a specific known bug for this issue, here are some possible causes:
1. Pipeline Validation/Refresh Issues
Sometimes during pipeline validation or when the canvas refreshes, snap configurations can revert to default states
This might happen if there are temporary connectivity issues with the SnapLogic platform
2. Browser/Session Issues
Browser cache problems or session timeouts might cause configuration changes to not persist properly
Multiple users editing the same pipeline simultaneously could cause conflicts
3. Platform Updates
Occasionally, platform updates might affect how snap configurations are stored or retrieved
Recommended Solutions
Immediate Actions:
- 1.
Document Your Settings: Keep a record of which parameters should have expression toggles enabled
- 2.
Version Control: Use SnapLogic's project versioning to track when changes occur
Preventive Measures:
- 1.
Clear Browser Cache: Regularly clear your browser cache and cookies
- 2.
Single User Editing: Avoid having multiple users edit the same pipeline simultaneously
If the Problem Persists:
Contact SnapLogic Support: Since this affects multiple parameters simultaneously and happens with snaps that haven't been opened recently, this could be a platform issue that needs investigation
Provide Details: When contacting support, include:
- 1.
Specific snap types affected
- 2.
Timeline of when the issue occurs
- 3.
Browser and version information
- 4.
Whether it happens across different projects/environments