Exportable markings causing issues in VS Code editor

All of a sudden I just started getting error like:

The error Internal Error: AttributeError: 'NoneType' object has no attribute '__dict__' indicates that a NoneType object is being accessed in your code where an object with the __dict__ attribute is expected. This is likely due to a variable or result being None and not properly handled.

Suggestion:
This is an internal error in Foundry, and you may not have direct access to the underlying issue. I suggest contacting Palantir support for further assistance. They can analyze the environment setup and configuration to identify the root cause.

If possible, ensure that any function or variable in your code is properly validated and isn't returning None unexpectedly. If it is related to your code, review areas where objects are being created or fetched.

If you suspect an issue in your environment setup, ensure proper configuration as mentioned in the documentation around retries or schema extraction:

Documentation Links Used:
Retries - Foundry APIs Local Environment
Retries - Dataset Metadata Operations Local Environment
Next Steps:
Since this appears internal, reach out to Palantir support for a detailed resolution.


Dismiss
Missing transform attribute

A NoneType object does not have an attribute __dict__'. Did you mean: '__dir__. Please check the spelling and/or the datatype of the object.

Details
Jump to line
foundry_pyls.utils.DiagnosticException: Internal Error: AttributeError: 'NoneType' object has no attribute '__dict__'. Did you mean: '__dir__'?

And

The Code Workspace has an egress policy (or source) applied to it which doesn't allow exporting one of the markings of the previewed datasets.
    We cannot allow previewing with this dataset as it may result in unintended data exfiltration.

    Please restart your workspace without checkpoint if you previously previewed a different transform in order to reset the workspace's egress policies.
    Otherwise, make sure to allow the dataset's markings in the Source's export control settings.
    (errorInstanceId=6e090abc-d300-4ca9-bdcf-ee619b1d7c07)

For transforms that were previously working just fine. Are you applying some kind on maintenance?

I am still getting this error:

The Code Workspace has an egress policy (or source) applied to it which doesn't allow exporting one of the markings of the previewed datasets.
    We cannot allow previewing with this dataset as it may result in unintended data exfiltration.

    Please restart your workspace without checkpoint if you previously previewed a different transform in order to reset the workspace's egress policies.
    Otherwise, make sure to allow the dataset's markings in the Source's export control settings.
    (errorInstanceId=e141e83b-a200-4695-b0f6-572aec229b1f)

[error] × The Code Workspace has an egress policy (or source) applied to it which doesn't allow exporting one of the markings of the previewed datasets.
2026-02-28 14:53:31.001 [info]   │     We cannot allow previewing with this dataset as it may result in unintended data exfiltration.
2026-02-28 14:53:31.001 [info]   │ 
2026-02-28 14:53:31.001 [info]   │     Please restart your workspace without checkpoint if you previously previewed a different transform in order to reset the workspace's egress policies.
2026-02-28 14:53:31.001 [info]   │     Otherwise, make sure to allow the dataset's markings in the Source's export control settings.
2026-02-28 14:53:31.001 [info]   │     (errorInstanceId=53bf0517-342e-46a1-9bb4-a440861da6cf)
2026-02-28 14:53:31.002 [info]   Maestro version 0.727.0
2026-02-28 14:53:31.002 [info]     

Which makes zero sense. The REST API Connection was setup to enable export without marking. And nothing has changed in my setup. This transform was workign just fine, then just stopped working

also this works just fine from the code repo, just not vscode

OK, so I was able to resolve the error in VSCode related to markings by ensuring my organization was added in the Exportable Markings section. I have no idea why this error showed up randomly, or why the transform continued to work just fine from the legacy code repository editor. Palantir should look into this behavior and enable same defaults when exportable markings are enabled. Thank you to @nicornk for contacting me to provide a solution.