Answer
In a confirmed case, this was traced to a stale file_path/file_name value left on the relevant BINARY_OBJECT record (the one holding the person/business-unit picture referenced by the Org Chart flow) — rather than the expected embedded BLOB content, the record had leftover file-path/file-name values pointing at something that no longer resolves correctly, which is what triggers this generic-looking resource-load error. Clearing the file_path and file_name values from the specific affected BINARY_OBJECT record resolved it, letting the flow fall back to the record's actual embedded binary content instead of trying to resolve the stale file reference.