Replies: 3 comments
-
Function call failure means it took more than 45 seconds to retrieve data, which should be really rare. I have tenants with 3000+ users that don't suffer from timeouts anywhere. Is your function app in a location near you? It might just be added latency due to deploying in a wrong region. |
Beta Was this translation helpful? Give feedback.
-
Hiya Kelvin, We're seeing this on every attempt to load BEC - does line up with the 45 second timeout you mentioned. We'll try some other tenants/users. Chris |
Beta Was this translation helpful? Give feedback.
-
Hi, will it be possible to increase the timeout? My problem is I manage tenants in multiple regions. South Africa, EU-West and UK-West. I did my deployment in EU-WEST region. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Good day everyone.
I have been using CIPP for about a week now and it is working for the most part. I am however receiving the below error at random times in the portal, especially when accessing tenants with over 1000 users.
Function call failure
{ "status": 500, "data": "Function call failure", "message": "Request failed with status code 500" }
I have checked the permissions and have granted permissions again on Azure API permissions.
Version Frontend

Current: 2.4.0
Version Backend
Current: 1.9.0
Beta Was this translation helpful? Give feedback.
All reactions