Currently, the Edge successfully processes RPC v2 requests locally, but it does not propagate status updates back to the Cloud. When a persistent RPC request is initiated from the Cloud for a device connected via an Edge gateway, the status remains "Queued" on the Cloud, even after the Edge has finalized the transaction.
The Edge should synchronize the status of RPC v2 requests with the Cloud in real-time. This ensures that the Cloud-side state accurately reflects whether the request was successful, failed, or timed out at the Edge/Device level.
Current Limitations:
- RPC v1 status propagation is fully implemented and functional.
- RPC v2 status updates are currently localized to the Edge database only.

Currently, the Edge successfully processes RPC v2 requests locally, but it does not propagate status updates back to the Cloud. When a persistent RPC request is initiated from the Cloud for a device connected via an Edge gateway, the status remains "Queued" on the Cloud, even after the Edge has finalized the transaction.
The Edge should synchronize the status of RPC v2 requests with the Cloud in real-time. This ensures that the Cloud-side state accurately reflects whether the request was successful, failed, or timed out at the Edge/Device level.
Current Limitations: