“quota exceeded" error in SAP Build basic trial environment

[AS_]

Dear Community,

I am currently preparing for the C_LCNC_2406 (SAP Certified Associate - Low-Code/No-Code Developer - SAP Build) certification, which requires completion of the "Experiencing End-to-End SAP Build" system exercise ( https://learning.sap.com/learning-journeys/experiencing-end-to-end-sap-build ).
As part of this exercise, I am instructed to create a new process in SAP Build Process Automation using the provided SAP Build basic trial environment. Unfortunately, when attempting to create a new Process there, I encounter the following error:

Error

Permitted quota of 750 was exceeded (type: "project").

Correlation Id: e6afe57f-1cc0-47b7-64c8-762ce904183e

Has anyone experienced this issue before and knows how I can approach or resolve it?

I’ve already created a case in the SAP Learning help center, but the SAP Learning Support Team informed me that this issue lies outside their support scope as the trial environment is publicly hosted.

I truly appreciate any help or suggestions you can provide.

Best regards,
Anna

[Be_Abhishek]

Facing same issue

[AS_ · Accepted solution]

Hi everybody,

During the Partner Get Certified Academy for Low-Code/No-Code Developer – SAP Build (Europe) session on Thursday, we were provided with an explanation of the issue along with the following solution:

The learning page currently links directly to a Basic Trial subaccount that has been marked as inactive and is no longer maintained. While the link still allows you to log in, it may direct you to an outdated or incorrect trial environment.

To make sure we're using the correct subaccount for our trial user, we should follow these steps instead:

1. Log in to the Basic Trial workbook using your GE* trial account credentials:
   👉 https://trials.cfapps.eu10-004.hana.ondemand.com/

2. Open the SBPA Exercise inside the workbook.

   

3. Use the Build Lobby link within the workbook to access the environment.
   This is important — the workbook dynamically assigns the correct tenant based on your login.

According to what has been shared during the Academy session, this route ensures we are accessing the right and active tenant. Other links might still work superficially, but they could point to outdated systems that cause errors like the one we encountered.

Hope this helps others facing the same issue! 😊

Best regards,
Anna

[svlightowler · Accepted solution]

Thanks for posting this solution!