Legacy Dev Forum Posts

Austen | 2021-05-21 14:54:55 UTC | #1

We retrieve and store details of architect data table objects using the /api/v2/flows/datatables endpoint via the Java SDK. The data tables have a "schema" member which is only populated when the expand parameter is set to include it.

We have had issues with expand parameters causing us to hit the rate limit in the middle of a single SDK call, as the platform makes multiple calls internally to retrieve the data requested via the parameter and these calls can hit the rate limit. When this happens, it is not signalled back to the caller, so we now avoid expand parameters where possible.

Is there an alternative way to retrieve the schema data for a data table without using the expand parameter? If not, is it possible for such a call to hit the rate limit, and if it does, how would we know that has happened?

Thanks,

Austen

John_Carnell | 2021-05-21 19:51:13 UTC | #2

Hi Austen,

I just got done talking with the developers on the Dev tables. The only time (with Dev Tables) you would not get back data tables schema back is if the call would take longer than 10 seconds. In this case, the schema data would not be returned.

One way you could work around that is to first get all the data table ids and then call the GET /api/v2/flows/datatables/{id} endpoint with the individual record using --expand endpoint. If you still see problems with this, then this might be a bug and the dev recommended opening a ticket with our Care team.

If you do open a dev ticket make sure you do the following:

1. Try to get the inin-correlation-id http header for this specific call and include it in the ticket. The dev team can use that to check the service logs.
2. Include this link in the ticket.
3. Ask the care engineer to open a servops ticket. The servops engineer should be able to view this post and then know they have to talk with the data tables team.

I hope that helps.

Thanks, John Carnell Manager, Developer Engagement

Austen | 2021-05-21 19:59:30 UTC | #3

Hi John,

Thanks for the swift reply.

We had considered using the individual data table endpoint, but this also has schema as an expand parameter, so while we'd be looking at fewer calls behind the scenes, there is presumably still a situation where we could hit the rate limit?

The Java SDK spec for data table shows schema as an optional field (https://developer.genesys.cloud/api/rest/client-libraries/java/DataTable), but from looking at typical data values for it, it will presumably always be non-null for a valid data table. If so, can we assume it being missing definitely means a rate limit issue?

Thanks,

Austen

system | 2021-06-21 20:15:06 UTC | #4

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.

This post was migrated from the old Developer Forum.

ref: 11002