Invisible Color Correction Keyframes

Nearly every single clip in the timeline for the project I'm working on has a contrast or color adjustment transition from the start to the finish. There are no keyframes controlling this, the changes are just there.

I can't remember exactly, because my entire experience using Resolve has been wholly frustrating at every turn (before, I was having actual keyframes appearing as I copied/pasted settings to the color adjustment nodes, usually due to clips overlapping in the timeline and confusing the color workspace interface. Now, I wish I was still having that problem), but I do not believe these transitions were there before. I could be wrong, but it seems like Resolve simply decided to stop making the keyframes visible.

I've been having to manually add keyframes to every single clip to compensate for these invisible automation, but it's getting impossible to manage.

Specs (yes, I know my video card is ancient):

Resolve 15 beta

Operating System: Windows 10 Pro 64-bit (10.0, Build 16299) (16299.rs3_release_svc_escrow.180502-1908)
Language: English (Regional Setting: English)
System Manufacturer: MSI
System Model: MS-7693
BIOS: V22.4
Processor: AMD FX(tm)-8350 Eight-Core Processor (8 CPUs), ~4.0GHz
Memory: 16384MB RAM
Available OS Memory: 16332MB RAM
Page File: 7671MB used, 11092MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 96 DPI (100 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Not Available
Microsoft Graphics Hybrid: Not Supported
DxDiag Version: 10.00.16299.0015 64bit Unicode

Card name: NVIDIA Quadro K600
Manufacturer: NVIDIA
Chip type: Quadro K600
DAC type: Integrated RAMDAC
Device Type: Full Device
Device Key: Enum\PCI\VEN_10DE&DEV_0FFA&SUBSYS_094B10DE&REV_A1
Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
Device Problem Code: No Problem
Driver Problem Code: Unknown
Display Memory: 9151 MB
Dedicated Memory: 985 MB
Shared Memory: 8166 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)

I have never seen this happen on a consistent basis, but once in a blue moon I've seen what I call a "corrupted node" where there's a weird value that causes the system to react in weird ways. Usually what happens to me is it's a "phantom window" that comes and goes. I can usually solve it by resetting the entire node, rebuilding it from scratch, and leaving that bad node empty (or recreating it as needed). Then there's no problem.

My guess is that you do have a keyframe somewhere and that's what is causing the problem. If you're on Resolve 15, at least you have a little diamond-shape indicator now on the node showing when a keyframe exists. I would bet this is most likely the culprit.

It is fairly crucial to avoid cutting-and-pasting keyframes, and there's a bug where you have to go into the Gallery, right click in the gray area and choose "Apply Grades Using Keyframes," then go back and right-click again and choose "Apply Grades Without Keyframes," and then it will stick. The default should be no keyframes, but once in awhile it'll try to do this and wreak havoc. I've also had stabilization get pasted in a copied grade, and that's clearly a problem since no 2 shots will ever have the exact same stabilization. All you can do is keep a very close eye on pasted grades and make sure only what you want is carried across. It can work very well, so don't get discouraged.