- Getting Started
- Before You Begin
- How To
- Designing your App
- Events and Rules
- Rule: If-Then-Else
- Rule: Open a Page
- Rule: Open URL
- Rule: Close Pop-Over/Bottom Sheet
- Rule: Show Message
- Rule: Show/Hide Spinner
- Rule: Set Values
- Rule: Start Process
- Rule: Upload File to Storage Bucket
- Rule: Get File From Storage Bucket
- Rule: Create/Update Entity Record
- Rule: Delete Entity Record
- Rule: Add to Queue
- Function: And, Or, Not
- Function: Concat
- Function: Contains
- Function: Count
- Function: EndsWith
- Function: If
- Function: IsBlank
- Function: Length
- Function: List
- Function: StartsWith
- Function: Sum
- Function: Sort
- Function: Now
- Function: Today
- Function: Time
- Function: Year
- Function: Month
- Function: Day
- Function: Hour
- Function: Minute
- Leveraging RPA in your App
- Leveraging Entities in Your App
- Leveraging Queues in Your App
- Application Lifecycle Management (ALM)
- Basic Troubleshooting Guide
- Apps Troubleshooting and FAQs
- Apps On-Prem Troubleshooting
Apps Troubleshooting and FAQs
When saving Apps from App Studio, the following error message can occur:
"Connection to Apps service is lost."
-
You've lost internet connection. Apps requires an active internet connection to save changes you make to your app.
OR
- The reason for this error can be the fact that the App service uses WebSocket to save the App definition.
First, ensure that you have an active internet connection. If you are still facing issues then:
- Allow
apps-socket.uipath.com
to have long live connections by making sure you have theconnection: Upgrade
parameter in the header. This must be done with the help of your IT team. - Work with your IT or network team to understand how WebSocket traffic policies are being handled and alter them as needed.
- Allow WebSocket connections by making sure that
apps-socket.uipath.com
is not added to your proxy policy. This must be done with the help of your IT team.
There are two known issues when this message can be displayed. Depending on the situation described below, follow the appropriate Possible cause and Solution.
-
When previewing an app, the following error can occur, even if there are no errors:
"Errors in App"
-
This issue can occur when an app is imported in the Automation Suite environment from the cloud environment. The following error can occur when previewing or publishing an app, even if there are no errors in the tree view:
"Errors in App"
- One or more browser extensions can cause this error to occur.
- Apps built in the Apps cloud environment which have entities referenced in them, will not work when imported in the Automation Suite environment.
An error stating a process is not found can occur in runtime, even if the process is available in Orchestrator.
_
) character.
Setting the control value using the Set Values rule in the Page load event results in not setting the control value properly.
When custom list, table, list, and dropdown controls have a thousand or more records to display, the performance may get slower.
When in Apps design time, the default selected value is correctly displayed for the dropdown control, but when switching to runtime it is no longer displayed
When adding custom arguments in the process details page, the newly added arguments are not displayed in the resource panel for binding.
In some situations, app preview might not work in the first attempt.
When previewing or running an app from home page, the app does not load and can result in a blank page.
The start page of the app is not set. Since there is no start page set, the app cannot decide which page to run or preview.
An app exported from the cloud environment and imported into the Automation Suite one can have some missing bindings.
When you assign an app variable in the Assign file to app variable property in the Get File from Storage bucket rule, the app variable is not saved.
When using the dark theme for Apps, the user experience can be sub-optimal.
In some cases, when adding a new process the following error can occur:
"Process not found - click to replace"
You can only reference up to 20 processes in an app. If there are more than 20 processes, an error can occur on all processes.
When previewing an app, the displayed start page is not the correct one.
In certain situations, an invalid binding error is displayed, even though there are no errors.
Referenced entities may intermittently display an error.
- Message: Connection to Apps Service Is Lost
- Possible Cause
- Solution
- Message: Errors in App
- Possible Cause
- Solution
- Message: Process(Process_Name) Not Found.
- Possible Cause
- Solution
- Issue: Event on Page Load Not Working
- Solution
- Issue: Slower Performance
- Solution
- Issue: Default Selected Value Not Showing in Runtime
- Solution
- Issue: Custom Arguments Not Displayed
- Solution
- Issue: App Preview Does Not Work in the First Attempt
- Solution
- Issue: Unable to Preview an App or Run an App From the Home Page
- Possible Cause
- Solution
- Issue: Bindings Missing in App Imported From Cloud Environment
- Solution
- Issue: Variable Not Saved in the Get File From Storage Bucket Rule
- Solution
- Issue: Dark Theme User Experience Issues
- Possible Cause
- Solution
- Message: Process Not Found - Click to Replace
- Possible Cause
- Solution
- Issue: Incorrect Start Page Is Displayed When Previewing an App
- Possible Cause
- Solution
- Issue: Invalid binding error message is displayed
- Solution
- Issue: Entities intermittently display an error
- Solution
- Issue: Data Service records not populated correctly
- Solution