Actor <-> Actor Call on Cloudflare
I've encountered a serious blocking issue when deploying actor-core applications to Cloudflare Workers. My game server works perfectly in local development but fails on Cloudflare with CPU limit errors.
The Problem: When one actor makes an RPC call to another actor in Cloudflare Workers, the execution blocks indefinitely until Cloudflare throws a CPU time limit error. This happens specifically with actor-to-actor communication.
Environment:
- Works in local development (localhost)
- Fails when deployed to Cloudflare Workers
- Using actor-core v0.8.0
Question: Has anyone successfully deployed actor-core applications to Cloudflare Workers with actor-to-actor RPC calls? Is there a recommended pattern for handling this situation?
Any insights, workarounds, or solutions would be greatly appreciated!
The Problem: When one actor makes an RPC call to another actor in Cloudflare Workers, the execution blocks indefinitely until Cloudflare throws a CPU time limit error. This happens specifically with actor-to-actor communication.
Environment:
- Works in local development (localhost)
- Fails when deployed to Cloudflare Workers
- Using actor-core v0.8.0
Question: Has anyone successfully deployed actor-core applications to Cloudflare Workers with actor-to-actor RPC calls? Is there a recommended pattern for handling this situation?
Any insights, workarounds, or solutions would be greatly appreciated!
Build and scale stateful backends. Rivet Actors is a library for long-lived processes with durable state, realtime, and scalability. Easily self-hostable and works with your infrastructure.
1,419Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
