Server error - Did not get a ping response in time - DEV

Bug reports
1

Hi,

I’m working on a new service today and I get a lot of “server error” “did not get a ping response in time”.

Is there any issues today or is there any limitations on how many records the service can handle in dev?

image
image1728×885 43.6 KB

2

Hi! :slight_smile:

There are no reported issues today, but the DEV environment for services is quite sensitive and can be affected if anyone else is developing in Create while you are running the service. The problem can also appear if you have a especially heavy service.

Do you know if one of these cases could be the reason why it happened to you?

3

I have a web request that are parsing three fields to a runtime only object, the reponse from the web request contains 10 000 records.

I have been running this all day and it seems very unstable, as sometimes it works and other times it fails in handling the response into the runtime object.

4

Hi,

Dev Tools processing a lot of data in development environment may typically experience these issues. So yes, it is pretty limited, but it is not limited on “number of records” but a total of the load (memory, CPU) and also there is a ping timeout if it takes too long.

If you are processing a lot of records, I have seen this type of error when trying to persist a lot of records in a single batch. Not sure if that’s the case, but if so, you may try to persist in batches instead.

You may also try to execute the service endpoint from /api/services to see if it helps (i.e. to see if it is the devtools that times out, or the execution of the service itself)