ext resource reference got messed up

xyz xyz unfortunately not.
I don't know how I would go about reproducing it aswell. since like I said I didn't even end up changing the script for the class
or the bugged scenes for that matter

i was able to copy the projects files but its so dense that its nearly impossible to remove anything without the bug disappearing
which is a new observation I made. commenting out all the script's content stops the error messages

which prompted me to start trial and error my way through the script

commenting out these lines

SaveManager.On_Loading_Done.connect(on_post_load.bind(data))

func on_post_load(_data : Dictionary) -> void:
	SaveManager.On_Loading_Done.disconnect(on_post_load)

which are part of this code block

func on_save() -> Dictionary:
	var data : Dictionary = {}
	
	#data["nav_col_layers"] = nav_col_layers
	
	return data

func on_load(data : Dictionary) -> void:
	if data.is_empty():
		return
	
	#nav_col_layers.assign(data.get("nav_col_layers", []))
	
	SaveManager.On_Loading_Done.connect(on_post_load.bind(data))

func on_post_load(_data : Dictionary) -> void:
	SaveManager.On_Loading_Done.disconnect(on_post_load)
	#update_col_layers(true)

(normally non of the code is commented)

the errors disappear but i don't understand why.
the exact same script is copied under a different name and it works completely fine
(I.E. no parsing error that would cause the class name to not be available)

for context SaveManager is a autoload script and the code in question does not run when the errors appear
(checked with a print statement before)

I can't see any way to make an MRP without removing bits of code at a time.
yeah, no. I really tried multiple times. I can't see a way to make an MRP. hope the extra info helps. and thanks for responding

xyz that's honestly fair. i appreciate you trying to help
i thought maybe someone would know what's causing it.
thanks regardless

xyz sure, don't see how that would make sense but I have my workaround regardless. thanks

xyz I'll try to explain it more clearly.
the problem is pretty much the error. which if i read it correctly states that the given scenes cannot find the resource (which is a gdscript)
in the path defined by the scene.tscn file. and that it is unable to parse the scene

that is to say. my problem is not being able to use those scenes since they complain about the resource

but it confuses me because
A) the same script whilst showing the bug on the 3 culprit scenes is also placed inside a fourth scene with a nearly identical setup, the only difference i could pin point is that the working scene had the script in question added after i tried to modify the script
B) simply copying the script with a change to the path and manually changing the scene reference resolves the parse error
C) the script has no errors which would results in the class name not being available in the project
D) also since there are no errors in the script it doesn't make sense why the section of code i outlined in my response is failing
given that the same piece of code works as intended in another script
E) the scenes started throwing the parse error after trying to modify the script, but when i saved and launched the project no actual changes to the script had taken place.

the work around is to disable the code i outlined and using a different approach to do the same thing.
which in my case was to call the function in a deffered call instead of waiting for the signal of the autoload script
and for extra clarification that same signal is used in the same manner across the entire project

xyz yeah, but i wouldn't offload my entire project onto someone to sift through. which is why i tried to break it down but that didn't work out
it did help to try and break it down since i found a workaround. that works for me. i'll just cross my fingers it doesn't happen again

xyz that's like the first thing i always do with weird bugs
like CS 101 turn it off and on again lol.
i even tried to remove the scripts from the 3 scenes
reload the entire editor
run the project
make the changes back
reload again
and when i run the issue persists

xyz i wish i could. i want to know a proper solution to this so i can use it next time it happens