Actor Unexpectedly Stopped After 3600s Despite Longer Timeout Setting

The community member describes an issue where their actor unexpectedly terminated after running for 3600 seconds (1 hour), despite being configured with a 360,000 second timeout and an expected runtime of ~4 hours. The key points are that the actor was functioning normally until termination, there were no error logs or exceptions found, and partial results were successfully retrieved. The community member has questions about what caused the premature termination, if there are any platform limitations they should be aware of, and how they can ensure the actor runs for the full intended duration. The additional context provided is that the actor was designed to iteratively collect data over an extended period, and the early termination significantly impacts their data collection process. The community member is seeking advice on how to resolve this issue and prevent future occurrences.