Frequent ingress_expiry error on update calls

[h1teshtr1path1]

I am getting these errors on update calls on canisters frequently. How to tackle this?
Subnet Id : e66qm-3cydn-nkf4i-ml4rb-4ro6o-srm5s-x5hwq-hnprz-3meqp-s7vks-5qe

I would love to know the exact reason behind this and what steps are being taken to tackle this? As with increased activities in the ecosystem, these errors have become very frequent.

[jamesbeadle]

Yes I am getting this too.

[Severin]

Agent-JS 2.1.0 is Released!

Hello Jake The root of the first error you encountered is the fact that a client’s time can be ahead the replica’s time which receives the message. Moreover the time certified by the subnet’s nodes can differ from both those times as well. We are aware of the problem and we’re discussing different options to improve the situation. We should be able to communicate a more concrete plan soon. For the second problem, please note that the ingress expiry ensures that a subnet will not start executin…

[peterparker]

Follow-up:

Ingress Expiry Issue - Your Input Needed!

Hi everyone , Over the past few weeks, there have been several reports on the forum from devs encountering ingress expiry issues, such as the following: Error: ReplicaTimeError: Specified ingress_expiry not within expected range: Minimum allowed expiry: 2024-09-25 13:57:00.580809774 UTC, Maximum allowed expiry: 2024-09-25 14:02:30.580809774 UTC, Provided expiry: 2024-09-25 13:57:00 UTC While we provided some valid explanations and future improvements in various threads yesterday (for …