Unexpected 500 Errors on Multiple OCodeKit Modules — Anyone Else Experiencing This?

Questions
,
1

:bullseye: What is your goal?

I would like to understand whether other users are currently experiencing unexpected 500 errors on OCodeKit modules, and whether this might be related to a broader platform/runtime issue.

:thinking: What is the problem & what have you tried?

Since today, several of my scenarios have started failing with a generic [500] Internal Server Error on different OCodeKit modules.

What’s unusual:
• It affects multiple scenarios, including a production version that has been frozen and unchanged for 20 days.
• The failing modules vary from run to run.
• Some of the modules that fail are upstream and haven’t been modified in weeks.
• There is no detailed JavaScript error message — only the generic 500.

What I’ve tried:
• Rolled back to a fully working backup (no recent changes).
• Re-ran scenarios multiple times.
• Verified that no recent code modifications were introduced.

Despite this, the issue persists.

Has anyone encountered similar behavior recently?

1 Like
4

Hi @fono,

No issues on our side. Since 0CodeKit is a third party solution, it is imperative to contact their support: ClickUp Forms

Also, since there is a native Make Code app now, consider moving nay code execution to inside Make.

Cheers,
Henk

1 Like
5

+1 to no issues.

Keep in mind that 0CodeKit offers different endpoints- it’s highly possible that they are “living” on different servers, so as Henk mentioned - contact their support providing information about which endpoints you are using.

0CodeKit also offers Slack community support:

Have a nice day,
Michal

6

@fono I’m also experiencing 500 errors from 0codekit since the 26th.

I tested some very simple code snippets and those executed without any issues. However, my actual production code — which has been running fine for weeks — is now returning 500 status codes.

Have you contacted 0codekit support yet? Do you have any additional information on what might be causing this?

7

Same experience here. First, random 500 Errors appeared on several scenarios. Then, these 500 Errors turned into a mysterious 400 Error.

Context
The scenario is designed to execute the same OCodeKit Python script multiple times sequentially (between 5 and 10 times, depending on the number of batches to process). The executions are not parallel — they run one after another.

Issue

Randomly, the module fails with the following error:
[400] Bad request. Please check your parameters.
More details: Your code did not execute successfully:
[E] writeBufToFile(): Couldn’t write ‘7’ bytes to file ‘/sys/fs/cgroup/cgroup.subtree_control’: Resource busy
[E] enableCgroupSubtree(): Could not apply ‘+memory’ to cgroup.subtree_control in ‘/sys/fs/cgroup’.
nsjail MUST be run from root and the cgroup mount path must refer to the root/host cgroup to use cgroupv2.
[E] main(): Couldn’t setup parent cgroup (cgroupv2)

The failure is inconsistent:

  • Sometimes it happens on the first execution

  • Sometimes on the nth execution

  • When it occurs, the scenario never completes successfully

Important notes

  • The script itself is valid and works when executed individually

  • Other scenarios using OCodeKit may run without issues

  • The executions are sequential, not concurrent

Make Support indicated that OCodeKit handles the execution environment itself, and that Make only forwards the API request.

I’m trying to understand whether:

  • Anyone else has encountered similar cgroup / nsjail errors?

  • This could be related to repeated sandbox/container initialization?

  • There are best practices when chaining multiple OCodeKit executions in one scenario?

Any feedback or similar experiences would be greatly appreciated. Cheers !

8

Hallo,

same problem here as well. Wrote support already anyone else news from their support or are their any alternatives on the market to run python codes with libs etc.

Thanks!