APEX

I am experiencing critical performance and reliability issues with the extension:

1. Import Button Delay: The import button itself takes an extremely long time just to appear in the UI, making it very unstable and slow to even initiate a workflow.
2. Excessive Import Duration: When the import process finally runs, it takes a significant amount of time to complete.
3. Changes Not Applied: After waiting, the logs indicate that a pre-import export was performed, but the actual changes made to the local .apx files (such as modifying or removing components on a page) do not reflect in the application inside the APEX Builder at all. It acts as if the import never updated the metadata.

Here is what the output log shows:

[08/04/26, 15:58:32.135] [APEXLangCommandHandlers] [INFO ] 
[
{
"message": "The application was exported to ...\\apex-exports\\f101-3.sql before the Import was performed."
},
{
"message": "APEXlang versions: APEXlang Compiler 26.1.0+3102, APEX 26.1.0+3102"
}
]

Questions / Concerns:

1. Silent Failures / Performance: The import takes a long time and finishes without an explicit error or success confirmation for the import phase itself (only showing the pre-import backup export). Is there a bottleneck related to large applications or local performance when dealing with the full project structure?
2. Granular Page Imports: Is it possible to import or synchronize a single .apx page file individually? Having to compile and process the entire application structure for a minor page adjustment feels very heavy and slow for daily development workflows. I tried compressing it into a .zip file, but I still get a 400 error when importing.

Any guidance on how to troubleshoot why the changes are not being pushed to the database despite the command running, or if there is a faster way to handle single-page updates, would be greatly appreciated.