# Ingress expiry issue

**URL:** https://forum.dfinity.org/t/ingress-expiry-issue/33416
**Category:** Developers
**Created:** [July 19, 2024, 6:42pm UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416 "2024-07-19T18:42:35Z")
**Posts on this page:** 8
**Page:** 2

<div class="post-metadata">

### Author: ![jennifertran](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jennifertran/32/11558_2.png) [@jennifertran](https://forum.dfinity.org/u/jennifertran)
#### Post date: [September 23, 2024, 6:50pm UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/21 "2024-09-23T18:50:46Z")

</div>

Hello there,

In the latest AgentJS release, you can set a specific `replicaTime`. Can you please try that and see if it helps?

> [@Agent-JS 2.1.0 is Released!](https://forum.dfinity.org/t/agent-js-2-1-0-is-released/35090):
>
> Noteworthy Features This feature includes the v3 synchronous call API! Calls to mainnet are able to bypass polling using the new endpoint The HttpAgent allows you to set and read replicaTime, which it will maintain information about in order to handle disagreements between the client and replica about time. Fixes and improvements for the useAuthClient library Full release notes: [Release Release 2.1.0 · dfinity/agent-js · GitHub](https://github.com/dfinity/agent-js/releases/tag/v2.1.0)

---

<div class="post-metadata">

### Author: ![Alishan](https://avatars.discourse-cdn.com/v4/letter/a/d6d6ee/32.png) [@Alishan](https://forum.dfinity.org/u/Alishan)
#### Post date: [September 24, 2024, 9:14am UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/22 "2024-09-24T09:14:34Z")

</div>

> [@jennifertran](#):
>
> replicaTime

what should be its value replicaTime

---

<div class="post-metadata">

### Author: ![xalkan](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/xalkan/32/16076_2.png) [@xalkan](https://forum.dfinity.org/u/xalkan)
#### Post date: [October 6, 2024, 1:55pm UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/23 "2024-10-06T13:55:12Z")

</div>

It seems like the issue may be related to congested subnets, and that migrating to a less busy subnet could be a solution — see (1) in [Subnets with heavy compute load: what can you do now & next steps](https://forum.dfinity.org/t/subnets-with-heavy-compute-load-what-can-you-do-now-next-steps/35762)

Is there a recommended way to deploy a canister in a specific subnet, e.g., [https://dashboard.internetcomputer.org/subnet/4zbus-z2bmt-ilreg-xakz4-6tyre-hsqj4-slb4g-zjwqo-snjcc-iqphi-3qe](https://dashboard.internetcomputer.org/subnet/4zbus-z2bmt-ilreg-xakz4-6tyre-hsqj4-slb4g-zjwqo-snjcc-iqphi-3qe)?

---

<div class="post-metadata">

### Author: ![Vivienne](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/vivienne/32/29170_2.png) [@Vivienne](https://forum.dfinity.org/u/Vivienne)
#### Post date: [October 7, 2024, 7:58am UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/24 "2024-10-07T07:58:49Z")

</div>

`dfx canister create` takes a `--subnet` flag. You should be able to pick `4zbus` with that

---

<div class="post-metadata">

### Author: ![xalkan](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/xalkan/32/16076_2.png) [@xalkan](https://forum.dfinity.org/u/xalkan)
#### Post date: [October 7, 2024, 8:58am UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/25 "2024-10-07T08:58:59Z")

</div>

Thank you! Are there any drawbacks to using a less popular subnet such as `4zbus`?

---

<div class="post-metadata">

### Author: ![theoman42](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/theoman42/32/23829_2.png) [@theoman42](https://forum.dfinity.org/u/theoman42)
#### Post date: [October 7, 2024, 11:01am UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/26 "2024-10-07T11:01:47Z")

</div>

Relatedly, is there any way to cancel an update call if it’s not executed within 10 seconds, as to avoid hanging state changes?

@jennifertran @Vivienne

---

<div class="post-metadata">

### Author: ![YAP](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/yap/32/33025_2.png) [@YAP](https://forum.dfinity.org/u/YAP)
#### Post date: [October 7, 2024, 11:20am UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/27 "2024-10-07T11:20:35Z")

</div>

Once an update call has been submitted, you cannot unsubmit it from the protocol’s point of view. The expiry time guarantees that a call’s execution will not start if the subnet time exceed the expiry. If you submit calls with local time + 10s, then you get the intended behavior. However, note that 10s is rather short for a heavily loaded subnet.

---

<div class="post-metadata">

### Author: ![Vivienne](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/vivienne/32/29170_2.png) [@Vivienne](https://forum.dfinity.org/u/Vivienne)
#### Post date: [October 7, 2024, 11:30am UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/28 "2024-10-07T11:30:49Z")

</div>

In most cases you will be happier on a less busy subnet. Then only time that I can see it being a drawback is if you make a lot of calls to canisters on a specific busy subnet. Calls between subnets take substantially longer (at least 4 rounds extra) than if you call a canister on your own subnet

[Previous page](https://forum.dfinity.org/t/ingress-expiry-issue/33416.md?page=1)
