Error when deploying Cloud Code

Server Code
1

Application ID: 164B1AF3-FA53-458D-BC59-E793AA35CBCE
Error UID: B009DB07-9A3D-46F6-A838-2D142107235F

Backendless encountered an error while handling the request. An internal trouble ticket with ID bl-server:B009DB07-9A3D-46F6-A838-2D142107235F has been created and we will be investigating the issue.

Problem description

Describe what you did in console that led to the error. Please provide a description of what actually happens. Be descriptive: “it doesn’t work” does not describe what the behavior actually is. This will help us with reproducing the problem.

Steps to reproduce

Please describe steps to reproduce starting from the first action.

  1. deploy any cloud code.
2

Hi,

Following up with additional findings that may help diagnose the issue.

What triggered the issue:
The deployment failures started after I deployed SessionService.js following some code updates. Since then, no service or timer can be deployed — the failure affects all Cloud Code files equally, not just SessionService.js.

UUID artifact files:
UUID-named artifact files started appearing in my Cloud Code file list at exactly the same time deployments began failing. Each deployment attempt adds more of these files — they appear to be orphaned partial deployment artifacts that are not being cleaned up after a failed deploy. I can manually delete them, but new ones are created with every save or deploy attempt.

This appears to have created a vicious cycle:

  1. An initial deployment failure left behind orphaned artifact files
  2. Each retry attempt creates additional artifact files without cleaning up previous ones
  3. The accumulating artifacts may be pushing the deployment size toward or over the plan limit
  4. Which causes the next deployment to fail, creating yet more artifacts

Confirmed: this is not a code issue:
I have reviewed the SessionService.js code thoroughly and found no syntax errors or issues that would cause a deployment failure. Furthermore, the failure affects all services and timers equally — including files that have not been modified at all — which confirms the problem is platform-side and not related to the content of any specific file.

Impact:
All Cloud Code deployments are completely blocked. No services or timers can be updated.

Could you please:

  1. Clean up the orphaned UUID artifact files from my application’s Cloud Code deployment
  2. Investigate whether there is a platform-side issue causing deployment artifacts not to be cleaned up on failure
  3. Restore deployment functionality for my application

I also noticed a related ticket (#20270) from another user reporting a Cloud Code deployment size limit issue around July 22 — the timing overlaps with when my issue started, which may indicate a broader platform-side problem.

Thank you,
Olga

3

Resolved. The issue was caused by a corrupted deployment state after a failed deploy of SessionService.js. Deleting the service entirely from the API Services panel, cleaning up the UUID artifact files, and redeploying fresh resolved the deployment block. No platform-side intervention was needed in the end."

1 Like
4

Hi @Olga_Hanelt ,

Sorry for the delay in responding.

In your case, the error was caused by the description of one of the methods exceeding the maximum allowed length of 1,024 characters. This resulted in a database error, which was not properly handled by the deploy endpoint.

I have created an internal ticket to improve error handling for this scenario so that a clear, user-friendly error message is returned instead.

I’m leaving this comment in case you encounter the same issue again, so you’ll know how to resolve it.

Regards, Andriy

1 Like
5

Thanks Andriy!

That explains everything perfectly. The long prose comment blocks in the original file — particularly deleteAccount with its multi-paragraph REMINDERS and OPEN VERIFICATION ITEMS sections, and endSession with its detailed explanation of Fixed vs Estimated duration logic — were the culprit. Nothing to do with Unicode, file size, or anything else we spent days chasing.
The version I have now is well within that 1,024 character limit — each method description is a concise 2-4 sentence paragraph. And now I know the rule going forward: keep any single JSDoc description block under 1,024 characters.
Appreciate the feedback,
Olga

1 Like