trying to activate a standard netsuite bundle (extension) and im getting this Compiler error {"type":"error.SuiteScriptError","name":"155923","message":"Compiler was unable to compile the given input file.","id":null,"stack":["createError(N/error)"],"cause":{"message":"Compiler was unable to compile the given input file.","stack":["createError(N/error)","map(/SuiteBundles/Bundle 500777/ExtensionMechanism.Server/CompilersMapReduce/SassCompilerMapReduce.js:165)"],"name":"155923","data":{"response":null,"notifications":[]}},"notifyOff":false,"userFacing":true}

I keep getting this error over and over after the upgrade, can't activate any of my extensions either. I updated the SC Extension management bundle as well, but that didn't solve anything.

apparently the theme has to be updated for changes to Saas compiling. I did it for one customer and the issue was resolved but now I'm getting this on another customer that has a custom theme. Does this mean we will have to upgrade the theme ourselves before we can push any changes?

I made all the sass adjustments that the error log was advising, after that I was able to activate the extensions without issue. One day after, I didn't make any theme/sass/tpl changes, tried to activate and got a new error with no information on it. It's the same error message that Livio posted here

and suprisingly enough, im trying to activate a standard netsuite extension- SC order status - and im getting an error. It seems like the extension is not compatible with the new Dart Library

very weird, I believe there is something wrong with the SASS compiler, after trying to activate all the extensions and theme a couple of times in a row -without any single change- the extensions + theme get activated at some point, it doesn't make much sense to me, is not a consistent workaround

yes same here. i had to activate 3 times

same here, if the error message is “compiler was unable to compile the given input file” just try 3 times and will work, good thing now is that deploying a small change can take up to 40 minutes netsuite

LOL this is ridiculous. seriously thinking about switching over to shopify

I think NetSuite just made a lot of angry customers. Just when SuiteCommerce was finally stable for a few years

This is EVERY online platform right now. I wish it was just SC. The cloud is getting a bad rep.

Same issues here, you would think it is Sass related for the script name on the error but as you all said, after trying a few more times you are able to activate. netsuitenetsuite halo

far away from switching brother, just log a case, they will take care of this, it’s just a bug. Product team will take care of this as they did with many other issues in the past

their support team sucks.

We work in a very small community, @Livio. It's hard to keep morale on the up and up. It's rough out there now.

i understand @Chris but we have a business to run. This platform is not cheap. netsuite is not cheap

much appreciation to @Steve Goldberg for all his help and support. He is probably keeping a lot of SCA developers sane

❤️

just for the record - I don’t have any extension built by SC and I had this issue before

This error has the odor of a race condition in an async file operation. Almost like someone optimized a bit too far in the hope of reducing compile time.

is there an active defect/case number that can be referenced for this that I can attach a new support case to?

Could updating the Extension Manager version help to solve this issue? I'm experiencing the same situation trying to activate in the sandbox envrionment

I think the Extension Manager updates (at least in Production) are handled by NS. I could be wrong about that...

We pushed out a fix/update to the SCEM about 10 days ago, which should solve some of these errors but the vast majority of the ones we are getting in cases are because theme code is still not Dart Sass compliant

@Chris yes that is true, I need to request to update for the Extensions Manager, but I was wondering if this could possibly solve the issue of the Sass compiler failing on activation

Something else strange is going on with Extension Manager. I'm getting a "Pending" for the activation status when it looks like the activation already completed. The Map/Reduce Script Status screen is reporting complete for all 12 steps.

I am still receiving this error and I have checked the theme and the extensions we control and the gulp command does not return any issues. I have submitted a support ticket but they keep giving me the run around with either “the activation is not in an errored state” or “you need to check your theme and extensions against the gulp command”. This is so frustrating because the retry 2-3 times was working but now it seems it has only gotten worse. I had to retry today 5 times before it activated. I have tried looking into the custom records that pertain to the activation process but I cannot find anyway to debug this. Idk what else to do if anyone has any thoughts please let me know. I spoke with my CTO about this and he is bringing it up with our account rep Monday in hopes of getting some help through different channels.