I'm looking for guidance on a Retool Classic App JSON import problem. I'm not a software developer, but I'm using ChatGPT, OpenAI Codex, and Claude to help develop and maintain an operational application built in Retool.
The problem
I have an existing production Retool application called Operative Dashboard and a separate development/testing version called Operative β QA.
We've successfully built and tested new functionality in the QA app. The feature allows a user to select multiple games and assign a videographer to them, rather than assigning games individually.
We now need to transfer those additions into the production application without replacing the existing production configuration, resource connections, or unrelated functionality.
Our process has been:
Export the current production application as JSON.
Export the working QA application as JSON.
Have Codex identify the specific new components, queries, and configuration changes made in QA.
Create a modified copy of the production JSON that includes only those approved additions.
Test importing the modified JSON into a disposable Retool application before touching production.
The import fails with this error:
t.get is not a function
What we have already tested
We created a disposable application called ThrowawayTest to isolate the problem.
The following tests were performed:
Import test
Result
Original production JSON export
Successful
Complete QA JSON export
Successful
Production JSON with one additional query
Failed
Production JSON with a QA-bound query
Failed
Production JSON with an adjusted application compatibility flag and QA-bound query
Failed
Our testing indicates that both original exports are individually importable, but the modified production JSON fails when we add a new plugin/query definition.
We have also tested variations involving resource identifiers, application identifiers, page identifiers, and an application-level compatibility flag, without resolving the error.
We have stopped experimenting because we do not want to risk damaging the production application.
Environment and constraints
Retool Classic Apps
Retool Free plan
Production and QA applications are separate
Both applications use Supabase PostgreSQL resources, but connect to different database projects
The QA feature has already been tested successfully
We want to preserve the existing production application and its unrelated functionality
We understand that changes to our production application can become live immediately because release management is unavailable on our plan
My questions
- What does "t.get is not a function" typically indicate during a Retool Classic App JSON import?
Is this associated with incompatible serialized component/query definitions, missing internal metadata, application version differences, or something else? - Is manually combining portions of two exported Retool Classic App JSON files a supported operation?
If not, is there an official or recommended method to transfer selected queries, components, modals, JavaScript handlers, and layout changes from one Classic App to another? - Can we safely transfer these additions without replacing the entire production application?
For example, is there a supported way to copy components and queries between applications, or use Retool's editor to reconstruct the feature while preserving existing application behavior? - What is the best approach for transferring tested features from QA to production on a Free-plan Retool instance without a separate release-management workflow?
- Is there a supported way to inspect, validate, or repair a modified Retool JSON export before attempting an import?
A request regarding your response
I'm not a coder, so I would greatly appreciate a response that is technically specific but structured as step-by-step instructions I can pass directly to ChatGPT, Codex, or Claude.
Ideally, please identify:
The likely cause of the import error, clearly distinguishing confirmed facts from possibilities.
The safest supported approach for transferring the QA functionality.
Any Retool documentation, commands, or editor procedures that apply.
What technical information or sanitized JSON examples you would need to diagnose the issue further.
Any approach we should specifically avoid.
If the recommendation involves modifying exported JSON, please describe the required structure or metadata precisely rather than suggesting trial-and-error changes.
I can provide sanitized portions of the exports, the exact error details, and the differences between the working and failing versions if that would help.
My priority is to preserve the working production application while promoting the successfully tested QA changes safely and reproducibly.
Thank you for any assistance.