1. Every time a user opens a P2P chat with the bot, the event arrives and the SDK logs a Processor not found for event type... warning (or error) because the handler exists in registration but the actual callback chain is broken
2. P2P chat entered: Register a no-op lambda to suppress error spam: lambda data: None # No-op: suppress "processor not found" error log spam

TL;DR

Register no-op handlers for bot_p2p_chat_entered and im.message.recalled_v1 events to suppress error logs.

Guidance

• Register a no-op lambda for bot_p2p_chat_entered events using .register_p2_im_chat_access_event_bot_p2p_chat_entered_v1(lambda data: None) to prevent "processor not found" error logs.
• Add an empty handler for im.message.recalled_v1 events using .register_p2_im_message_recalled_v1(lambda data: None) to handle recalled messages without errors.
• Review the removal of the _pending_inbound_events queue mechanism to ensure it does not cause issues with event handling.
• Verify that these changes resolve the error logs and recalled message issues.

Example

# Register no-op handlers for events
.register_p2_im_chat_access_event_bot_p2p_chat_entered_v1(lambda data: None)
.register_p2_im_message_recalled_v1(lambda data: None)

Notes

The provided fix assumes that the no-op handlers are sufficient to resolve the issues. However, the removal of the _pending_inbound_events queue mechanism may require further review to ensure it does not cause problems with event handling.

Recommendation

Apply workaround: Registering no-op handlers for the specified events should resolve the immediate issues, but it is recommended to review the event handling design to ensure it meets the requirements of the application.