Meraki CCF Connector: getNetworkClients API Call Fails with 504 Timeout Due to Excessive Default Lookback Period

The Meraki CCF connector is consistently receiving HTTP 504 timeout responses when executing the getNetworkClients API call.

Investigation of the Meraki API request history shows that the connector is querying with a timespan (lookback period) of 2,592,000 seconds (30 days) and executing the request approximately every 1 to 15 minutes. Due to the volume of data returned for this time range, the API request appears to exceed processing limits and times out.

All other API calls made by the connector return HTTP 200 responses and successfully populate the associated custom log tables. The issue appears to be isolated to the getNetworkClients endpoint and is likely related to the large result set generated by the 30-day lookback period.

**Steps to Reproduce**
Configure and run the Meraki CCF connector.
Allow the connector to execute its scheduled API queries.
Review API request history in the Meraki Dashboard.
Observe that requests to getNetworkClients are submitted with a timespan of 2592000 seconds (30 days).
Note that the requests return an HTTP 504 timeout response.

**Expected Behavior**

The connector should successfully retrieve client data without timing out, or it should use a lookback period that is appropriate for the query frequency and expected data volume.

**Actual Behavior**

The getNetworkClients API call returns HTTP 504 timeout responses, preventing client data from being collected.

**Additional Evidence**
Meraki API request history can be exported from the Meraki Dashboard and shows the 504 responses for the affected endpoint.
Running the same API request manually via Postman with a significantly shorter timespan returns results successfully, indicating the timeout is related to the volume of data requested.

**Suggested Improvement**

Given that the connector executes frequently (approximately every 1 to 15 minutes), consider reducing the default timespan value from 2,592,000 seconds (30 days) to a smaller value that is less likely to cause timeouts, such as 86,400 seconds (24 hours).

This would reduce the amount of data returned per request while still providing sufficient coverage for ongoing data collection.