Hi there! 
I can see you’re experiencing a frustrating issue with operations getting stuck in Camunda Operate. This is actually a known problem that typically occurs due to synchronization issues between Zeebe, Operate, and Elasticsearch.
Classification: This is a Problem - operations are not behaving as expected.
Based on your description, this appears to be caused by one or more of the following:
Most Common Causes:
- Elasticsearch Index/Shard Issues - Missing or corrupted indices (like
operate-process-*) can cause operations to hang indefinitely - Data Inconsistency - Process instances may exist in Elasticsearch but not in Zeebe, causing operations to fail silently
- Importer/Exporter Pipeline Problems - The synchronization between Zeebe and Elasticsearch may be disrupted
- Resource Bottlenecks - Low disk space, memory, or CPU can stall the import/export pipeline
Troubleshooting Steps (Without Losing Data):
Before we proceed with more specific solutions, I need some additional information:
- What version of Camunda 8 are you using? (format: major.minor.patch)
- Are you running SaaS or Self-Managed?
- What’s your deployment setup? (Docker, Kubernetes, etc.)
Immediate Actions You Can Try:
-
Check Elasticsearch Health:
- Verify all required indices exist and are healthy
- Look for shard allocation issues
- Check disk space and resource usage
-
Review Logs:
- Check Zeebe, Operate, and Elasticsearch logs for errors around the time operations get stuck
- Look for import/export errors or timeouts
-
Restart Services (Ordered):
- Restart Operate first, then Zeebe
- This can help resynchronize the state without data loss
-
Resource Check:
- Ensure adequate disk space, memory, and CPU for all components
References:
Could you please provide the version and environment details so I can give you more targeted assistance? Also, if you can share any relevant log entries from when the operations get stuck, that would be very helpful! 