CDA 500 Interval Offset

CLI Script

getusgs-timeseries

Describe the bug

Hello,
So I’ve been knocking out SWF's getUSGS stuff this month and I noticed a problem with some gages where they pop “CDA Error[500]” Example line being:
2026-08-21 15:42:07;INFO;Attempting to write values for ts_id --> PNRT2.Flow.Inst.15Minutes.0.Decodes-U,08032700.00060
2026-08-21 15:42:07;ERROR;CDA Error: response=<Response [500]>
I went into the log from swf's cda to check it out and the line was:
ORA-20110: ERROR: Incoming data set contains multiple interval offsets. Unable to store data for PNRT2.Stage.Inst.15Minutes.0.Decodes-U
From there I went into Cwms-Vue to check out the timeseries interval offset and it's set to 0s just like the original timeseries this guy is a replacement for. Dug into usgs just in case and it matches all the relevant numbers including the interval of course. Deleted the ts and remade it from scratch just in case it was a bad plug in and still got a 500.

Followed the steps from https://www.hec.usace.army.mil/confluence/cwmsdocs/ccm/getusgs-script-using-cda-198935663.html for setting up each location+timeseries. Out of 750 about 90 got this 500 error and I'm not 100% on what's the common thread. Like if you check 5, 2 were that the interval transmissions changed from 15 minutes to 5 minutes and needed that adjustment, but the other 3 are still 15 minutes on https://waterdata.usgs.gov/nwis/uv?format=rdb&site_no=08032700&period=PT7D for instance. That link is for the gage I used for the example error lines.

REDACTED relevant log output

getUSGS log line
2026-08-21 15:42:07;INFO;Attempting to write values for ts_id -->  PNRT2.Flow.Inst.15Minutes.0.Decodes-U,08032700.00060
2026-08-21 15:42:07;ERROR;CDA Error: response=<Response [500]>

catalina.out log line
ORA-20110: ERROR: Incoming data set contains multiple interval offsets. Unable to store data for PNRT2.Stage.Inst.15Minutes.0.Decodes-U

Steps to Reproduce

No response

Start with the getusgs-timeseries CLI script and compare the logged failing timeseries with the CDA and USGS records linked in the report. Investigate why affected writes produce the multiple-interval-offset ORA-20110 error, including cases that remain at 15 minutes. Done means the common failure condition is reproducible and affected gages can be written successfully without the CDA 500 error.