Studio Web: all workflow saves failing with InternalServerError (autosave 500) — existing solution won't open, SBPA integration also failing with 404

Help Studio Web
, ,
1

Hi all,

We’re facing what looks like a backend persistence issue with Studio Web on our Enterprise org, showing up as three related symptoms. Posting here in parallel with a support ticket in case others have hit this or UiPath staff can help.

Symptom 1 — New workflows fail on autosave (~20 seconds after creation)

Steps to reproduce:

  1. Go to https://cloud.uipath.com/<myorg>/studio_/projects
  2. Create a new RPA workflow
  3. Editor opens fine, but after ~20 seconds the first autosave fires and fails:
Saving workflow failed — InternalServerError
at UiPath.StudioWeb.Blazor.Services.WorkflowService.SaveAndUploadWorkflowAsync
   (WorkflowService.cs: lines 717/930/938/968)
at UiPath.StudioWeb.Common.Utils.RetryHelper.RetryAsync (RetryHelper.cs: line 71)
at UiPath.StudioWeb.Blazor.Controllers.BlazorWorkflowDesigner.SaveWorkflowAsync
   (BlazorWorkflowDesigner.cs: line 256)

So the read path works (projects open) but every save/upload fails, even after built-in retries. Reproducible 100%, for multiple users.

Symptom 2 — Existing solution returns 500 on open

Our existing solution fails to load entirely:

Http failure response for
https://cloud.uipath.com/<myorg>/studio_/backend/api/Project/ad80a739-803a-480d-9d3c-a7f7b2432146?api-version=2
: 500
Error ID: 788790abccda4c6eb11320665bb28638

We suspect it was left in an inconsistent state by a failed save.

Symptom 3 — SAP Build Process Automation → UiPath integration fails creating automations

SAP_SBPA_1_00009: Could not create UiPath automation. code: 1002,
Could not find the requested resource. (#ERR8989002), status 404
Correlation ID: 50865bc1-12e2-49e8-6e85-a89167a1985e

Since SBPA provisions the project through the same Studio Web backend, we believe this is the same root cause.

Already ruled out: licenses (Automation Developer seats available, reallocated for affected users), sessions (signed out everywhere, tested incognito, cookies/pop-ups allowed), browser (multiple browsers/machines), and status.uipath.com shows no incident.

Has anyone seen Studio Web autosave failing org-wide like this? Is there any tenant-side setting that affects the Studio Web storage/persistence layer, or is this purely a backend issue for UiPath to resolve? Support ticket is raised — sharing the Error ID and Correlation ID above in case staff here can trace them.

2

@loginerror Can you please help here.

3

@loginerror @Ioana_Gligan @silviu_tanasie @Ricardo_Rosales1 @andras.palfi @Pavel_Dragan @loredana_ifrim @Samrat_Dutta @Bianca.Dragu @Andrei_Vintila @marian.platonov
Can you please help on this. or tag someone who might have an idea.

Due to the complex nature of our license I can not raise the technical support ticket to UiPatch directly.

4

Hi @kartik.metkar thanks for reaching out! Give me some time to forward this to my colleagues. Thank for your patience :folded_hands:

5

Thought process from me:

  • Identify the failing backend service using:

    • Error ID: 788790abccda4c6eb11320665bb28638
    • Correlation ID: 50865bc1-12e2-49e8-6e85-a89167a1985e

  • Validate and repair the tenant’s Studio Web project repository.

    • Check for corrupted project metadata.
    • Remove orphaned records.
    • Rebuild project indexes if required.

  • Verify Studio Web storage connectivity.

    • Confirm artifact storage is reachable.
    • Validate read/write permissions for the tenant.
    • Repair broken storage mappings.

  • Repair the affected project:

    • Inspect project ad80a739-803a-480d-9d3c-a7f7b2432146.
    • Restore project metadata from a healthy state if corruption is found.
    • Recreate the project repository entry if necessary.

  • Reprovision Studio Web services for the tenant.

    • Refresh tenant configuration.
    • Re-register Studio Web resources.
    • Validate project creation and save operations.

  • Revalidate SAP Build Process Automation integration.

    • Re-establish provisioning connections.
    • Test automation creation from SBPA.
    • Confirm resource lookup APIs return valid responses.

  • Implement backend safeguards.

    • Enable transactional save operations.
    • Prevent partial saves from corrupting project state.
    • Add consistency validation before project commits.

Actions

  • Keep the support case open and request escalation to:

    • Cloud Operations
    • Studio Web Engineering Team

  • Provide:

    • Tenant Name
    • Project ID
    • Error ID
    • Correlation ID
    • Approximate failure timestamps (UTC)

  • Use UiPath Studio Desktop as a temporary workaround until the backend repository issue is repaired.

Expected Outcome After Fix

  • New Studio Web workflows save successfully.
  • Existing projects open without HTTP 500 errors.
  • SAP Build Process Automation can create UiPath automations successfully.
  • Autosave functions normally across all users in the tenant.

Based on the evidence provided, this looks like a backend repository/storage corruption or provisioning issue affecting the entire tenant, and a permanent fix will require intervention from UiPath Engineering, not a configuration change by administrators or end users.

6

@kartik.metkar - We have applied a fix, please retry opening your projects. Feel free to get back to us on this thread if something still does not work as expected.

7

Thanks a lot for you input /thoughts.

8

Thanks, this will help me.

9

@flavius Thanks a ton.

Our 2 issues (Symptom 2 & 3 from my post) are solved and working fine.

However Symptom 1 is still there.
Created new RPA Workflow from Studio Web and click anywhere on screen so that Auto save get called,
I am getting attached error on screen (same as mentioned in post).

image
image1588×860 155 KB

10

Thanks for confirming Symptoms 2 and 3 are resolved.

For Symptom 1: for organizations integrated with SAP, SBPA (SAP Build Process Automation) is the primary, supported path for creating and managing these workflows, and you should use this path. Creating workflows directly in the Studio Web portal is a secondary path for these organizations, and that’s specifically where the autosave failure is occurring.

So for now, please create/manage these workflows through SBPA rather than directly in the Studio Web portal. We’re actively fixing the portal-creation path and will post back here once it’s rolled out.

11

Hi @kartik.metkar

Based on the symptoms, this looks more like a tenant/backend persistence issue than a browser, license, or local Studio Web problem.

The fact that:

  • New workflows can be created but autosave consistently fails with HTTP 500

  • Multiple users are affected

  • An existing solution also returns 500 while loading

  • SAP Build Process Automation integration is returning 404

  • The issue reproduces across browsers and machines

strongly suggests an issue with the Studio Web project storage/persistence backend or tenant configuration.

Since you have already raised a Support ticket, I would recommend providing UiPath Support with the Error ID, Correlation ID, affected project ID, approximate timestamps, and affected user accounts so they can trace the backend requests.

As a quick isolation test, you could also try creating/saving a workflow in another UiPath organization/tenant, if available. If that works, it would further confirm that the problem is tenant-specific rather than browser/client-side.

I wouldn’t recommend repeatedly recreating or modifying the affected solution until Support confirms the backend state, especially since the existing project may already be in an inconsistent state.

Hopefully UiPath Support can identify the tenant-side issue from the Error ID and Correlation ID. :+1: