I call my remote service but it is not yet up.
When it is started it received all missed rpc calls.
But it is not needed now (the train has gone).
So how can I understand on service level that it received outdated requests that nobody wait a reply to?
There isn’t a way to inspect requests and determine if they’re outdated I’m afraid. The best you could do with Nameko 2.x is put something in your method signature.
However, there is a PR adding proper RPC timeouts into the Nameko 3.x prerelease branch. With this feature, you can specify an expiration for a request and it will be removed by the broker if it hasn’t been consumed in time. So the functionality you desire is coming soon (in Nameko 3)
Thanks, will wait until 3.x is released.