# Ingress\_expiry not within expected range error

**URL:** <https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456>\
**Category:** Motoko\
**Tags:** Functional-Programming, community-consideration, Frontend\
**Created:** [September 23, 2024, 1:03pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456 "2024-09-23T13:03:28Z")\
**Posts on this page:** 20\
**Page:** 3

<div class="post-metadata">

**Author:** ![jamesbeadle](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jamesbeadle/32/10110_2.png) [@jamesbeadle](https://forum.dfinity.org/u/jamesbeadle)\
**Post date:** [October 2, 2024, 11:31am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/42 "2024-10-02T11:31:16Z")

</div>

Ok so I needed to add around 22 trillion cycles but then was able to run:

```auto
dfx canister update-settings --compute-allocation 1 data_canister --ic

```

And currently I have no ingress expiry error:

 ![image](https://us1.discourse-cdn.com/flex023/uploads/dfn/original/3X/0/8/0864f3887454e4d62a25044c509deb8acdc3c2f3.png)

Will see how it goes.

---

<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:** [October 2, 2024, 11:54am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/43 "2024-10-02T11:54:58Z")

</div>

after this command were you issues fixed or not?  
@jamesbeadle

---

<div class="post-metadata">

**Author:** ![jamesbeadle](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jamesbeadle/32/10110_2.png) [@jamesbeadle](https://forum.dfinity.org/u/jamesbeadle)\
**Post date:** [October 2, 2024, 12:01pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/44 "2024-10-02T12:01:17Z")

</div>

I dunno, this works on one of my canisters through the candid UI but I need to redeploy all and see if it was just computationally expensive canister or every canister I need has to be set with this, including the frontend canisters…

So far if you set this on canister you don’t get the ingress expiry error through the candid UI as i did before.

---

<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:** [October 2, 2024, 12:07pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/45 "2024-10-02T12:07:14Z")

</div>

once you check it on all canister then please share your feedback also, thanks

---

<div class="post-metadata">

**Author:** ![Manu](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/manu/32/3999_2.png) [@Manu](https://forum.dfinity.org/u/Manu)\
**Post date:** [October 2, 2024, 1:02pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/46 "2024-10-02T13:02:14Z")

</div>

Sorry you are experiencing issues! Could we please in all reports include

- canister id
- subnet id
- exact error message
- which agent are you using and which version  
so we can appropriately address the issues?

@jamesbeadle which canister id did you see problems with? Was it addressed with the compute allocation?

---

<div class="post-metadata">

**Author:** ![TusharGuptaMm](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/tusharguptamm/32/11944_2.png) [@TusharGuptaMm](https://forum.dfinity.org/u/TusharGuptaMm)\
**Post date:** [October 2, 2024, 1:04pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/47 "2024-10-02T13:04:07Z")

</div>

I came across this solution as well, but it typically implies we’re bidding for compute resources, which will significantly increase the cycles burn rate? As far as I know, setting “compute-allocation 1” still consumes cycles, when idle? [Clarity on compute-allocation](https://forum.dfinity.org/t/clarity-on-compute-allocation/5700)

---

<div class="post-metadata">

**Author:** ![HinzaAsif](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/hinzaasif/32/18076_2.png) [@HinzaAsif](https://forum.dfinity.org/u/HinzaAsif)\
**Post date:** [October 2, 2024, 5:13pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/48 "2024-10-02T17:13:00Z")

</div>

I am very concerned about how we manage our projects if errors arise on ICP after updates. My project has been stuck for more than a month due to an update, and I am continuously paying development costs.

@Manu @jennifertran, please look into this project. Our platform is based on content publishing and community contribution, and if our community is unable to contribute, it defeats the purpose of our platform.

Regards

---

<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:** [October 2, 2024, 7:07pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/49 "2024-10-02T19:07:04Z")

</div>

Hello @HinzaAsif,

1. Is there a specific error that you are running into?

2. When did this start occurring?

3. What is the ID of the canister that is error is appearing in?

---

<div class="post-metadata">

**Author:** ![HinzaAsif](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/hinzaasif/32/18076_2.png) [@HinzaAsif](https://forum.dfinity.org/u/HinzaAsif)\
**Post date:** [October 2, 2024, 7:20pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/50 "2024-10-02T19:20:25Z")

</div>

@Alishan is the person working on the project, and he created this post 9 days ago.  
@jennifertran, I would really appreciate it if you could resolve this issue. Our production work is on hold, and the whole team is stuck.

Regards

---

<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:** [October 2, 2024, 7:24pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/51 "2024-10-02T19:24:51Z")

</div>

Hello @Alishan,

I know that you sent me the subnet ID previously. However, can you please also send me the additional information? Please feel free to DM.

- canister id
- Which agent are you using and which version?
- Are you setting any custom expirations on messages?

---

<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:** [October 3, 2024, 6:39am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/52 "2024-10-03T06:39:08Z")

</div>

@jennifertran  
canister= ogidd-6aaaa-aaaal-qcezq-cai  
agent version is= “@dfinity/agent”: “^0.18.1”,  
and i am not setting any custom expirations

---

<div class="post-metadata">

**Author:** ![Mysticx](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Mysticx](https://forum.dfinity.org/u/Mysticx)\
**Post date:** [October 3, 2024, 6:39am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/53 "2024-10-03T06:39:30Z")

</div>

@jennifertran I’d like to mention that our canisters: `rxqpk-hyaaa-aaaam-actvq-cai` and `pvvqb-hiaaa-aaaam-ab6xq-cai` have the same code as the canister in question: `7uioq-vyaaa-aaaal-ac6ea-cai`. but the later is on a different subnet. This is the subnet in which our working canisters are : `https://dashboard.internetcomputer.org/subnet/4ecnw-byqwz-dtgss-ua2mh-pfvs7-c3lct-gtf4e-hnu75-j7eek-iifqm-sqe`  
and this is the subnet in which our canister with issue is : `https://dashboard.internetcomputer.org/subnet/6pbhf-qzpdk-kuqbr-pklfa-5ehhf-jfjps-zsj6q-57nrl-kzhpd-mu7hc-vae`. there is a very visible difference between the number of canister in the two subnets: 23’915 v 6’281.

---

<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:** [October 4, 2024, 1:42am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/54 "2024-10-04T01:42:25Z")

</div>

Thank you to @Alishan, @Mysticx, and any others who sent me the info via DM. It is known that the canisters that you are having issues with are on subnets with heavy compute load.

Here is an update on our end:

> [@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):
>
> Hi everybody! In the recent weeks, we’ve seen the demand for computation on ICP significantly increase. This is of course great news, but also leads to some challenges. We now see that there are quite some subnets that are running at or almost at maximum compute capacity. This means that canisters have to wait for their turn to compute and therefore messages are processed with much higher latency. You may notice ingress messages get rejected with an error saying “timed out waiting to start execu…

---

<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:** [October 4, 2024, 6:22pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/55 "2024-10-04T18:22:09Z")

</div>

Also which one are you using? The Javascript one?

---

<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:** [October 4, 2024, 6:34pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/56 "2024-10-04T18:34:37Z")

</div>

Yes, i am using JavaScript .

---

<div class="post-metadata">

**Author:** ![rumenov](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/rumenov/32/13632_2.png) [@rumenov](https://forum.dfinity.org/u/rumenov)\
**Post date:** [October 4, 2024, 7:33pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/57 "2024-10-04T19:33:04Z")

</div>

Hi @Alishan

If you are really using the JS agent it means you [are using 1 year old agent](https://www.npmjs.com/package/@dfinity/agent/v/0.18.0).

Is there chance that you upgrade to the most recent one ?

---

<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:** [October 5, 2024, 12:57am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/58 "2024-10-05T00:57:41Z")

</div>

I have two projects and both are using same same agent one is working and other is not, and there canisters are on different subnet , canister on which i am facing this error is on such subnet which has 24k+ canisters and the other canister which which is working fine is on such subnet that have only 6k+ canisters. I can think it might be due to load of canisters,  
And the solution provided by @jennifertran i think temporary because if i migrate my canister to another subnet after one or two years later load increased also on that subnet again i will face this issue, and if increase computational rate/ cycles burn rate , it may also cause of issue when others people also increase it,  
I am looking a professional way to sort it out.  
Thank @rumenov

---

<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:** [October 5, 2024, 1:13am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/59 "2024-10-05T01:13:17Z")

</div>

Hello @Alishan

Have you reviewed this post in detail? [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)

If you are not looking to migrate the canisters to a different subnet (which might be overloaded in the future), you can try to use compute allocation.

You can also wait for the long term solutions that we are looking to implement.

---

<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:** [October 5, 2024, 2:04am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/60 "2024-10-05T02:04:47Z")

</div>

Thank @jennifertran.  
I am using next js and my website is article base and their seo really needed. For that purpose i have to generate static pages to add metadata because crawler didn’t pick metadata of clients page mean if i add metadata to the page after loading JavaScript, for that reason i have to generate static pages each time and deploy them again on IC . I have to repeat this process once in a day so that articles which were created on website to be generated as static.  
**What nextjs do**  
it get all ids of my articles and generate static page of each article or id, during this process it send query to canister to get data of article by id and generate its page. As this process really fast and send to many requests to canister for example if there are 500 articles, it will call a canister 200 time which i think not a good approach. Do you suggest me alternative solution for seo. What i do so that my problem of again and again next js build generation and deployment to be sorted.

---

<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:** [October 5, 2024, 2:07am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/61 "2024-10-05T02:07:13Z")

</div>

Reason to do this only for SEO please suggest me the best solution which were already implemented and working. @jennifertran @rumenov @peterparker and other all people,  
Thanks in advance.

[Previous page](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456.md?page=2)

[Next page](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456.md?page=4)
