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.

Hi Apify Community,
I have a question about the $5 monthly platform credit for free users:
When users consume their free credits on our actor, does Apify compensate developers for these credit-based usages?
I'd appreciate any clarification on how the payment system works with free credits.
Thanks! 🙏

Hi. I only want to retrieve tweets where users directly mention me in the tweet, not tweets that mention me because they are replies to tweets that mentioned me. Can you do this? For more details on this issue, please refer to: https://devcommunity.x.com/t/how-to-differentiate-direct-reply-and-mentions/149262.

Thanks.