using standard methods to identify the final and start values of the accumulating properties, and picking a datetime that lies inbetween the two ranges usually works to bridge a discontinuity for charting applications. here however that does not seem to take - the example is:

#discontin begin
/solarquery/api/v1/sec/datum/list?nodeId=739&startDate=2024-12-24T16%3A20&endDate=2024-12-26T04%3A00&sourceIds=/AWB4/S1/R2/GEN/1&offset=0&max=15

created,localDate,localTime,nodeId,sourceId,watts,frequency,wattHours
2024-12-24T16:20:00Z,2024-12-24,11:20,739,/AWB4/S1/R2/GEN/1,-29146,60.016,84360188
2024-12-24T16:21:00Z,2024-12-24,11:21,739,/AWB4/S1/R2/GEN/1,-31027,60.005,84360703
2024-12-24T16:22:00Z,2024-12-24,11:22,739,/AWB4/S1/R2/GEN/1,-33284,59.995,84361234
2024-12-24T16:23:00Z,2024-12-24,11:23,739,/AWB4/S1/R2/GEN/1,-34140,60.005,84361813
2024-12-24T16:24:00Z,2024-12-24,11:24,739,/AWB4/S1/R2/GEN/1,-35341,60.012,84362398
2024-12-24T16:25:00Z,2024-12-24,11:25,739,/AWB4/S1/R2/GEN/1,-35975,60.013,84363000
2024-12-24T16:26:00Z,2024-12-24,11:26,739,/AWB4/S1/R2/GEN/1,-35129,59.995,84363578
2024-12-24T16:27:00Z,2024-12-24,11:27,739,/AWB4/S1/R2/GEN/1,-30716,60.021,84364109
2024-12-24T16:30:00Z,2024-12-24,11:30,739,/AWB4/S1/R2/GEN/1,134461.29749472,,11205.10812456
2024-12-24T16:35:00Z,2024-12-24,11:35,739,/AWB4/S1/R2/GEN/1,129354.02570160,,21984.61026636
2024-12-24T16:40:00Z,2024-12-24,11:40,739,/AWB4/S1/R2/GEN/1,134461.29749472,,33189.71839092
2024-12-24T16:45:00Z,2024-12-24,11:45,739,/AWB4/S1/R2/GEN/1,153183.31565040,,45954.99469512
2024-12-24T16:50:00Z,2024-12-24,11:50,739,/AWB4/S1/R2/GEN/1,171905.33380608,,60280.43917896
2024-12-24T16:55:00Z,2024-12-24,11:55,739,/AWB4/S1/R2/GEN/1,197437.04768592,,76733.52648612
2024-12-24T17:00:00Z,2024-12-24,12:00,739,/AWB4/S1/R2/GEN/1,217861.48977264,,94888.65063384

the auxilliary record exists:

#list aux records for R2
/solaruser/api/v1/sec/datum/auxiliary?withoutTotalResultsCount=true&nodeIds=739&sourceIds=/AWB4/S1/R2/GEN/1&startDate=2024-01-22T00:00:00.000&endDate=2024-12-29T00:00:00.000

created,localDate,localTime,meta,nodeId,samplesFinal,samplesStart,sourceId,type,updated
2024-12-24T16:28:00Z,2024-12-24,11:28,"GeneralDatumMetadata{pm={ecogyEvent={id=solarnetwork-event-3538a833-112b-4b37-a2d2-2222e1a7d759, path=/AWB4/S1/R2/GEN/1, type=solarnetwork, cause=discontinuity, final=

{wattHours=84364109}

, start=

{wattHours=11205.10812456}

, userId=4d67264b-f743-4ee1-9ccf-d62db9ea0454, created=2025-01-23T02:24:09.965Z, endDate=2024-12-24T16:28:00.000Z, location=

{node=739, site=S1, device=GEN/1, system=R2, project=AWB4}

, priority=1, userName=John.Telyon Admin Support, datumType=Reset, startDate=2024-12-24T16:28:00.000Z, description=discontinuity}}, }",739,{a={wattHours=84364109}},{a={wattHours=11205.10812456}},/AWB4/S1/R2/GEN/1,Reset,2025-01-23T02:24:10.343285Z

a stale command was issued for those days (there were other aux records also created on 25th and 26th):

#stale
/solaruser/api/v1/sec/datum/maint/agg/stale?startDate=2024-12-23T00:00&endDate=2024-12-27T12:00&nodeIds=739&sourceIds=/AWB4/S1/R2/GEN/1

but the "data spikes" in the Hour aggregate still remained, whereas the 5 Minute resultuiion charts were fine for the same datetime range.