Actor Unexpectedly Stopped After 3600s Despite Longer Timeout Setting

Subject: Actor Unexpectedly Stopped After 3600s Despite Longer Timeout Setting

Issue Description:
Our actor unexpectedly terminated after running for 3600 seconds (1 hour), despite:
• Configured timeout: 360,000 seconds
• Expected runtime: ~4 hours (for iterative data collection)
• No error logs or exceptions found
• Results were partially received

Key Points:

1. The actor was functioning normally until termination
2. No error messages in logs
3. Partial results were successfully retrieved
4. Termination occurred during planned iteration process

Questions:

1. What caused the premature termination?
2. Are there any platform limitations we should be aware of?
3. How can we ensure the actor runs for the full intended duration?

Additional Context:
The actor was designed to iteratively collect data over an extended period, and the early termination significantly impacts our data collection process.

Please advise on how to resolve this issue and prevent future occurrences.