Power Platform Community Forum Thread Details

Hi Everyone,

Can someone help me with this error in PowerApps? Suddenly I cannot save my app and showing this error.

Error saving to document server. Code: failedToSave Error: undefined is not a valid argument for URI
StackLength: 1435
Stack: Error: <MESSAGE REMOVED>
at new i (https://content.powerapps.com/resource/webauth/v3.25064.3.337661004/studio/js/Core.js?v=3.25064.3.337661004:2:302505)
at new e (https://content.powerapps.com/resource/webauth/v3.25064.3.337661004/studio/js/Core.js?v=3.25064.3.337661004:2:102412)
at e._upsertDynamicResourceConfig (https://content.powerapps.com/resource/webauth/v3.25064.3.337661004/studio/js/Core.Services.js?v=3.25064.3.337661004:2:517173)
at https://content.powerapps.com/resource/webauth/v3.25064.3.337661004/studio/js/Core.Services.js?v=3.25064.3.337661004:2:518819
at y (https://content.powerapps.com/resource/webauth/v3.25064.3.337661004/studio/js/Core.js?v=3.25064.3.337661004:2:100833)
at e.<anonymous> (https://content.powerapps.com/resource/webauth/v3.25064.3.337661004/studio/js/Core.Services.js?v=3.25064.3.337661004:2:518283)
at https://content.powerapps.com/resource/webauth/v3.25064.3.337661004/studio/js/Core.js?v=3.25064.3.337661004:2:541581
at Object.next (https://content.powerapps.com/resource/webauth/v3.25064.3.337661004/studio/js/Core.js?v=3.25064.3.337661004:2:541686)
at a (https://content.powerapps.com/resource/webauth/v3.25064.3.337661004/studio/js/Core.js?v=3.25064.3.337661004:2:540392)
at c.Class.derive._oncancel.then (https://content.powerapps.com/resource/webauth/v3.25064.3.337661004/studio/openSource/modified/winjs/js/base.js?v=3.25064.3.337661004:2:44325)

Session ID: b5713079-bdc5-4915-88a8-c2feca7dedab

Categories:

General Questions

@SM-11070337-0,

Based on the images provided, you're encountering an "Error saving to document server. Code: failedToSave

Error: undefined is not a valid argument for URI" in Power Apps. This error typically indicates an issue with how Power Apps is trying to save your application, often related to invalid characters, corrupted settings, or a temporary service issue.

Power Apps Studio Cache/Browser Issues:

Sometimes, local cache or browser-related issues can interfere with Power Apps Studio's functionality.

Solution:

Clear Browser Cache and Cookies: This is a common first step for many web application issues.
Try a Different Browser: Test if the issue persists in another web browser (e.g., if you're using Chrome, try Edge or Firefox).
Try Incognito/Private Mode: This opens a browser session without extensions or cached data, which can help rule out browser-specific problems.

Data Source Issues:

Corrupted Data Source Connection: While less common for a general save error, an unstable or corrupted connection to a data source (e.g., SharePoint list, Dataverse, SQL Server) could theoretically interfere with the saving process if Power Apps is trying to validate something related to it during the save.

Solution:

Refresh Data Sources: Go to "Data" in Power Apps Studio and try refreshing your data sources.
Reconnect Data Sources: If refreshing doesn't help, consider removing and re-adding your data sources (make sure to back up any complex formulas first).

Power Apps Service Interruption:

Occasionally, there might be temporary issues with the Power Apps service itself.

Solution:

Check Service Health: You can check the Microsoft 365 Service Health Dashboard to see if there are any known Power Apps outages or incidents in your region.
Wait and Retry: If there's an ongoing service issue, you might just need to wait for Microsoft to resolve it and then try saving again later.

failedToSave Error:

undefined is not a valid argument for URI": This suggests that something in the data or configuration being sent to the Power Apps saving mechanism is not correctly formatted or contains an unexpected value (represented by "undefined") where a valid URI (Uniform Resource Identifier) is expected.

Common Causes and Solutions:

Corrupted App Settings/Screens/Controls:
Invalid Characters: Check if you've recently added any unusual or special characters to control names, screen names, or variable names. Sometimes, characters that are fine in other contexts can cause issues in Power Apps' saving process.
Copy-Pasting Issues: If you've copied and pasted controls or screens from other apps or even within the same app, there might be underlying corruption or conflicting properties that are not immediately visible.

Solution:

Isolate the Problem: Try to identify what recent changes you made before the error started appearing.
Revert Recent Changes: If possible, use version history in Power Apps to revert to a previous working version of your app and then re-implement your changes more carefully.
Rebuild Problematic Parts: If you suspect a specific screen or set of controls, try recreating them from scratch in a new, empty screen. Move your logic over incrementally to see if the error reappears.

Temporary Files and Storage:

The error message mentions "document server." While Power Apps handles the saving, sometimes temporary files or storage issues can occur.

Solution:

"Save to Computer" (from your second image): This is a crucial workaround! If you can't save directly to the cloud, use the "Save to Computer" option. This will download a .msapp file of your application.
Once downloaded, you can then try to upload this .msapp file as a new app in Power Apps Studio (or overwrite an existing one if you're comfortable). This often "cleans" the app and resolves saving issues.
Immediate Steps to Take (Based on your images):
Click "Save to Computer": This is the most important immediate step. It will ensure you don't lose your recent changes.
Try to open the downloaded .msapp file:
Go to Power Apps (make.powerapps.com).
Click "Apps" on the left navigation.
Click "New app" > "Canvas" > "Open" (or "Upload file" if that option is more prominent).
Select the .msapp file you just downloaded. This will create a new app from your local file.
Try saving this new app. If it saves successfully, it indicates a problem with your previous app's cloud instance. You can then continue working on this newly created app.

If the problem persists after "Save to Computer" and re-uploading:

Simplify Your App: If possible, try removing some of the most recently added controls, formulas, or data sources to see if you can isolate what's causing the problem.

Create a Blank App: As a test, create a completely new, blank canvas app and try saving it. This will help determine if the issue is with your specific app or with Power Apps Studio in general.

By following these steps, especially utilizing the "Save to Computer" option, you should be able to recover your work and troubleshoot the underlying cause of the saving error.'

🏷️ Please tag me @MS.Ragavendar if you still have any queries related to the solution or issue persists.

✅ Please click Accept as solution if my post helped you solve your issue and help others who will face the similar issue in future.

❤️ Please consider giving it a Like, If the approach was useful in other ways.