Skip to Content (Press Enter)
2023-09-02 22-03-06
Tristan Steed
52Views
3Comments
Solved
Request Failed with error {Post request}
Question
Debug
Service Center

I'm encountering an issue with a specific record on a screen where I set up two queries upon initialization. For this one particular record with its unique ID, I consistently receive popup alerts indicating a failed request error. Strangely, this error only appears for this specific record; other records in the system work perfectly fine when I navigate to the same screen.

I've taken a few steps to troubleshoot the problem. I checked the error logs in the service center, and I noticed that the error gets logged multiple times whenever I visit that screen. Unfortunately, the details provided in the service center don't specify the origin of the error—no widget ID or error type is mentioned. It simply states that it was a post request. Due to this lack of specific information, I suspect it might be related to a server action causing this issue.


gets logged multiple times 

No useful information logged outside of it being a post request 

0
0
30 Nov 2023
Copy Link
2023-09-02 22-03-06
Tristan Steed
Solution

Thank you so much for your input! Your suggestion led me to discover the root cause of the issue. It turns out that the server actions were timing out specifically for that particular record due to the immense number of employees associated with that company.

Here's what I found: Each time an employee record was loaded on the screen, it triggered the loading of 52 web blocks. Each of these web blocks had a query set to fetch data upon screen initialization. Consequently, when the screen was accessed for this company, a total of 52 server actions were simultaneously running for each employee (query's ran at start).

To address this, I modified the query settings to fetch data only on demand, resolving the problem entirely. The reason why this specific record experienced timeouts was solely due to the high volume of queries triggered by the significant number of employees associated with that company. Other companies remained under the timeout threshold as they had just enough employees to stay within the acceptable time limits

See solution in context
2
0
30 Nov 2023
Copy Link
2024-05-08 06-29-37
Prince Aadil Khan Panwar
Solution

Hi Tristan Steed, 

as it shows 

then try to read this 


try to do this 

hope this helps

Thanks 

Prince

1
0
30 Nov 2023
Copy Link
2023-09-02 22-03-06
Tristan Steed

I am going to mark this as the solution as it led me to discover the root cause of the issue.

0
0
30 Nov 2023
Copy Link
2023-09-02 22-03-06
Tristan Steed
Solution

Thank you so much for your input! Your suggestion led me to discover the root cause of the issue. It turns out that the server actions were timing out specifically for that particular record due to the immense number of employees associated with that company.

Here's what I found: Each time an employee record was loaded on the screen, it triggered the loading of 52 web blocks. Each of these web blocks had a query set to fetch data upon screen initialization. Consequently, when the screen was accessed for this company, a total of 52 server actions were simultaneously running for each employee (query's ran at start).

To address this, I modified the query settings to fetch data only on demand, resolving the problem entirely. The reason why this specific record experienced timeouts was solely due to the high volume of queries triggered by the significant number of employees associated with that company. Other companies remained under the timeout threshold as they had just enough employees to stay within the acceptable time limits

2
0
30 Nov 2023
Copy Link
Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.