Setting alarm and onStateChange
Hello, I'm using onStateChange to propagate state to firestore DB. And it seems to me that onStateChange is called even when there is no actual state changed for example I can see following logs:
Writing to Firestore: http://127.0.0.1:8081/v1/projects/teamday-ai/databases/(default)/documents/aiChatV2/0UwNVUblr3HvhkD8SjaX
level=INFO msg="scheduling event" ccl=true t=1757490470340
Writing to Firestore: http://127.0.0.1:8081/v1/projects/teamday-ai/databases/(default)/documents/aiChatV2/0UwNVUblr3HvhkD8SjaX
level=INFO msg="setting alarm" timestamp=1757490470340
Document written successfully to emulator: projects/teamday-ai/databases/(default)/documents/aiChatV2/0UwNVUblr3HvhkD8SjaX
Document written successfully to emulator: projects/teamday-ai/databases/(default)/documents/aiChatV2/0UwNVUblr3HvhkD8SjaX
I would assume that internals wouldn't trigger onStateChange - am I missing something here?
Writing to Firestore: http://127.0.0.1:8081/v1/projects/teamday-ai/databases/(default)/documents/aiChatV2/0UwNVUblr3HvhkD8SjaX
level=INFO msg="scheduling event" ccl=true t=1757490470340
Writing to Firestore: http://127.0.0.1:8081/v1/projects/teamday-ai/databases/(default)/documents/aiChatV2/0UwNVUblr3HvhkD8SjaX
level=INFO msg="setting alarm" timestamp=1757490470340
Document written successfully to emulator: projects/teamday-ai/databases/(default)/documents/aiChatV2/0UwNVUblr3HvhkD8SjaX
Document written successfully to emulator: projects/teamday-ai/databases/(default)/documents/aiChatV2/0UwNVUblr3HvhkD8SjaX
I would assume that internals wouldn't trigger onStateChange - am I missing something here?
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
Similar Threads
Was this page helpful?
