requests keep failing due to an old starttime argument value that is no longer present anywhere in the config

[sideview-nick]

I had solved this once already I thought, by manually kicking the starttime keys that the app wrote into the conf, so that they were less than 720 hours before the current time.

However the problem came back and in 1.3.1 it seems maybe worse. I'm sure there's a simple answer but looking for guidance.

Lots of request fail because there is an argument being passed for starttime of 2025-07-31.
I do think that was the day I originally installed the app but that timestamp is not present anywhere in my conf at this point. Is the app itself perhaps pulling it from kv store, as a kind of 'cursor time' ?

2026-02-06 13:18:04,570 log_level=ERROR pid=3384079 tid=MainThread file=base_modinput.py:log_error:317 | Get error when collecting events.
Traceback (most recent call last):
File "/opt/splunks/10.0.0/etc/apps/ta_cisco_webex_add_on_for_splunk/lib/splunktaucclib/modinput_wrapper/base_modinput.py", line 141, in stream_events
self.collect_events(ew)
File "/opt/splunks/10.0.0/etc/apps/ta_cisco_webex_add_on_for_splunk/bin/webex_meetings_summary_report.py", line 89, in collect_events
input_module.collect_events(helper, ew)
File "/opt/splunks/10.0.0/etc/apps/ta_cisco_webex_add_on_for_splunk/bin/input_module_webex_meetings_summary_report.py", line 121, in collect_events
meeting_usage_reports = paging_get_request_to_webex(
File "/opt/splunks/10.0.0/etc/apps/ta_cisco_webex_add_on_for_splunk/bin/webex_api_client.py", line 79, in paging_get_request_to_webex
raise e
File "/opt/splunks/10.0.0/etc/apps/ta_cisco_webex_add_on_for_splunk/bin/webex_api_client.py", line 40, in paging_get_request_to_webex
data,response_header = make_get_request_to_webex(
File "/opt/splunks/10.0.0/etc/apps/ta_cisco_webex_add_on_for_splunk/bin/webex_api_client.py", line 198, in make_get_request_to_webex
raise e
File "/opt/splunks/10.0.0/etc/apps/ta_cisco_webex_add_on_for_splunk/bin/webex_api_client.py", line 188, in make_get_request_to_webex
response.raise_for_status()
File "/opt/splunks/10.0.0/lib/python3.9/site-packages/requests/models.py", line 1024, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://webexapis.com/v1/meetingReports/usage?from=2025-07-31T00%3A00%3A01Z&to=2026-02-05T18%3A18%3A04Z&max=100

Thanks in advance for any way to reset this to get it to start.

Also, in case it's related I'm getting a steady diet of these errors.
In the very initial setup I did have a value for siteurl, but this triggered errors that we have no such site in our Webex account (technically our webex account is very small and it seems to not use/have any sites at all).

2026-02-06 13:18:04,569 log_level=ERROR pid=3384079 tid=MainThread file=base_modinput.py:log_error:317 | [-] Error happened while getting date from webex https://webexapis.com/v1/meetingReports/usage?from=2025-07-31T00%3A00%3A01Z&to=2026-02-05T18%3A18%3A04Z&max=100 API: code: 400 - body: {"message":"The request could not be understood by the server due to malformed syntax. See 'errors' for more details.","errors":[{"description":"Required request parameter 'siteUrl' for method parameter type String is not present"}],"trackingId":"ROUTERGW_b4fcb8d2-40f9-4308-80a3-2d278b1d8c71"}
[!] You need to re-configure the account in configuration page

[ifonsecam]

Hi @sideview-nick, thanks for reporting these issues.

The site URL is required in order to get data from that endpoint, it follows this format https://sitename.webex.com, in the field of the input you will need to enter sitename.webex.com. Please take a look to this article to find your Webex site.

Also, with the Splunk App for Lookup File Editing you can verify (and change) if that date is being pulled from the KV Store, it probably was the last checkpoint that was saved.

[sideview-nick]

Ah! Well that makes sense. Yes if I put the site url in there then that problem goes away.

As a suggestion, your app should not label this as "Site Name". The label in the configuration page should probably say "Webex Site URL" instead. Also a little explanatory text or an example might go a long way.

I saw "Site Name" in the URL when I was filling out that screen and thought this was some Webex Proper Noun for office locations that I hadn't encountered yet, and I just typed in the city that our main office is in hoping it would become clear later. It didn't occur to me that Site Name might mean the company's URL on webex.com

eg: Note in globalConfig.json you have this:

                    {
                        "field": "site_url",
                        "label": "Site Name"
                    }