automatelab/automation-error-index huggingface dataset:
Platform: Power Automate
Category: schema
Error: InvalidRequestContent. The request content was invalid and could not be deserialized.
Error code: InvalidRequestContent
Cause: A required field in the action payload (commonly the approval assignedTo, or an attachment property) is null or uses an incorrect property name.
Fix: Check the run detail to see which field is null/malformed. For approvals, ensure Assigned To has a valid user email and is never blank. For attachments, use the content property formatted as {"name": "<file>", "content": "<base64>"}. Re-run after fixing the payload.
Platform: Power Automate
Category: auth
Error: ConnectionAuthorizationFailed. The caller does not have the minimum required permission on connection.
Error code: ConnectionAuthorizationFailed
Cause: The flow maker or running account lacks permission to use one of the connections referenced in the flow.
Fix: In My Flows, open the flow > Edit > Connections and re-authorize or replace any connection with a warning icon with one owned by or shared with the running user. In solutions, update the connection reference. Verify the user has at least the Environment Maker role.
Platform: Power Automate
Category: schema
Error: Resource not found for the segment '<EntitySetName>'.
Cause: A Dataverse action references an entity set name or custom process action that is incorrect, misspelled, or inactive.
Fix: Confirm the logical collection (plural) name by opening the table in a Solution > See solution layers. Use the exact logical collection name (e.g. cr123_customentities, not 'Custom Entities'). If it is a custom process action, verify it is Active under Settings > Processes. Re-save and test.
Platform: Power Automate
Category: auth
Error: Principal user is missing prvCreate<EntityName> privilege.
Cause: The service account or user running the Dataverse action has a security role lacking the required Create/Read/Write privilege on the target table.
Fix: In Power Platform admin center > Users + permissions > Users, select the user and Manage security roles. Assign a role with the required privilege on the target table (Basic User is often the baseline). Re-run; use Run diagnostics on the user to confirm privileges.
Platform: Power Automate
Category: config
Error: The Dataverse Database for this environment is not ready yet.
Cause: Approval flows auto-provision a Dataverse database on first run; that provisioning is still in progress or has failed.
Fix: In Power Platform admin center, confirm the environment's Dataverse database shows Ready. If provisioning failed, recreate the database or open a support ticket. Once Ready, rerun the flow. Ensure the running user has a Power Automate per-user/per-flow license to satisfy provisioning prerequisites.
Platform: Power Automate
Category: config
Error: Create an approval action failed. Possible cause could be invalid users assigned for approval.
Cause: The email passed to an approval's Assigned To field does not correspond to a valid user in the organization's Azure AD.
Fix: Verify the email is a licensed Microsoft 365 user in the same tenant; guest accounts need the tenant to allow guest approvals. Replace hard-coded addresses with dynamic content from a trigger/lookup and test with a known-valid internal address. Confirm the user is not deleted/disabled in Azure AD.
Platform: Power Automate
Category: timeout
Error: Flow run timed out. Please try again.
Cause: The Power Automate UI timed out waiting for a response; the flow itself is usually still running in the background (a UI-side timeout, not a cancellation).
Fix: Check My Flows > Run history - the flow likely still ran or succeeded. If an action is genuinely slow, reduce its retry policy from the default 8 retries to a custom policy (e.g. 3 retries, 5s). For flows over 30 days, split long segments into child flows via Run Child Flow.
Platform: Power Automate
Category: config
Error: MailboxNotEnabledForRESTAPI. The mailbox is either inactive, soft-deleted, or hosted on-premise.
Error code: MailboxNotEnabledForRESTAPI
Cause: The Office 365 Outlook connector cannot reach the mailbox because it is on-premises Exchange, lacks an Exchange Online license, or was soft-deleted.
Fix: Confirm the user has an active Microsoft 365 license including Exchange Online. If on-premises, configure Exchange hybrid and enable the REST endpoint, or migrate to Exchange Online. Re-authorize the Outlook connector after assigning the license to refresh the token.
Platform: Power Automate
Category: config
Error: Your flow has been suspended because it is in violation of your organization's Data Loss Prevention policies.
Cause: A DLP policy classifies two or more connectors used in the flow in different data groups (Business vs Non-Business), suspending the flow automatically.
Fix: In Power Platform admin center > Data policies, find the policy affecting your environment and identify the offending connector combination. With an admin, move the connectors into the same data group or create an environment-specific policy permitting the combination. Then turn the flow back on.
Platform: Power Automate
Category: schema
Error: Send an HTTP request to SharePoint failed: Cannot find resource for the request.
Cause: The SharePoint REST URI points to a list, library, or resource that does not exist at the specified relative URL.
Fix: Double-check the relative URL (e.g. _api/web/lists/GetByTitle('<ExactListTitle>')) - the title is case-sensitive. Confirm the list/library was not renamed. If the site URL changed, update the Site Address. Test _api/web/lists in a browser to enumerate available lists.
Platform: Power Automate
Category: connectivity
Error: HTTP request failed: A connection attempt failed because the connected party did not properly respond.
Cause: The HTTP action could not establish a TCP connection within the timeout, typically because the host is unreachable, firewalled, or slow.
Fix: Verify the target URL is publicly reachable and not firewall-blocked; whitelist Power Automate outbound IPs if behind a corporate firewall. Confirm the endpoint supports TLS 1.2+. Configure a custom retry policy and higher timeout on the HTTP action. For on-premises endpoints, use the on-premises data gateway.
Platform: Power Automate
Category: schema
Error: OpenApiOperationParameterValidationFailed. SendEmailV2 is missing required property 'Attachments/ContentBytes'.
Error code: OpenApiOperationParameterValidationFailed
Cause: The Send an email (V2) Attachments array is missing the ContentBytes property, usually because the attachment object was built without all required fields.
Fix: Construct each attachment with both Name and ContentBytes: {"Name": "<file>", "ContentBytes": "<base64>"}. Use outputs('Get_file_content')['body/$content'] for the base64 content. Do not mix ContentBytes (V2) with the older Content property. Test by sending to yourself first.
Platform: Power Automate
Category: schema
Error: ExpressionEvaluationFailed: the result of the evaluation of 'if' condition expression is not boolean
Error code: ExpressionEvaluationFailed
Cause: An expression using dynamic values fails at runtime because the actual data is a different type or null — something the engine cannot catch at save time.
Fix: Open the failed run, select the action, and inspect Inputs for the actual value. Guard null-prone references with if(empty(...)) or coalesce(). Validate types before conversion (e.g. isInt() before int()). For dates, pass an explicit format to formatDateTime()/parseDateTime().
Platform: Power Automate
Category: other
Error: ActionFailed: An action failed. No dependent actions succeeded
Error code: ActionFailed
Cause: A connector action returned a 4xx/5xx from the downstream API, or a called child flow failed; Power Automate wraps the real error in this generic status.
Fix: Open the failed run and expand the action's Outputs to read the real API error and status code, then fix per status (400 bad input, 404 missing, 5xx downstream). To run an action even after a prior failure, set 'Configure run after' to include 'has failed'. For child flows, drill into the child run history.
Platform: Power Automate
Category: rate-limit
Error: Rate limit is exceeded. Try again in N seconds
Error code: 429
Cause: The connector enforced its per-timeframe throughput quota (HTTP 429); each connector sets its own limit independent of the daily API request quota.
Fix: Set the action's Retry Policy to Exponential Interval to back off on 429. Honor any Retry-After header with a Delay in a Do Until loop. Reduce call frequency by filtering data upstream; for Dataverse, review Service Protection limits and batch with ExecuteMultiple.
Platform: Power Automate
Category: rate-limit
Error: FlowRunQuotaExceeded: too many requests were made at the same time
Error code: FlowRunQuotaExceeded
Cause: The user/tenant consumed all daily Power Platform API request actions for their license tier (e.g. 6,000/day seeded, 40,000/day Premium).
Fix: Check consumption in Power Platform admin center > Analytics. Cut actions per run: replace Apply to Each with Select/Filter array, add OData $filter/$top to Get items, reduce polling frequency. If the workload needs it, upgrade to a Premium/Process license; short term, spread runs across flows or off-peak.
Platform: UiPath
Category: install
Error: UiPath Studio 2024.10.1 EEUI / 1603 install error
Error code: 1603
Affected versions: 2024.10.1
Cause: The EEUI - InitializeEmbeddedUI failure with MSI exit 1603 on UiPath Studio 2024.10.1 happens when endpoint protection kills rundll32.exe ; whitelist the installer, install .NET 4.8.1 plus ASP.NET Core 8.0, and re-run
Platform: UiPath
Category: other
Error: GlobalVariablesNamespace
Error code: CS0246
Cause: The CS0246 GlobalVariablesNamespace error fires during library compilation at publish time, even though the project runs fine in the Studio designer
Platform: UiPath
Category: other
Error: Cannot find the UI element corresponding to this selector
Cause: The selector recorded at design time no longer matches the live element at runtime, typically because the target renders dynamic attributes (title, idx, aaname) that change between sessions.
Fix: Open the activity and use Indicate on Screen to re-record against the live app. Anchor to a stable parent and replace volatile attributes with wildcards (*). Increase the activity Timeout for slow-loading pages. Enable SimulateClick/SimulateType to bypass full selector resolution for input activities.
Platform: UiPath
Category: timeout
Error: Activity timeout exceeded
Cause: A UI Automation activity could not locate or interact with the target element within its Timeout, usually because the app is slow to render or the robot runs unattended without an active desktop.
Fix: Increase the activity's Timeout (default 30s). Enable SimulateClick/SimulateType so it works without a visible desktop. Add Wait for Ready: Complete or an explicit delay before the interaction. For unattended robots, ensure the session is logged in and unlocked.
Platform: UiPath
Category: other
Error: The process cannot access the file because it is being used by another process
Cause: An Excel file stays locked by a prior Excel activity or an orphaned Excel.exe because the Application Scope was not closed cleanly, or multiple branches access the same file at once.
Fix: Wrap all Excel operations in one Excel Application Scope (or Use Excel File) so the handle is released on exit. Avoid Append Range in loops; accumulate rows in a DataTable and write once. Kill lingering Excel processes with a Kill Process activity at the start. Ensure no conflicting Excel instance is open.
Platform: UiPath
Category: config
Error: Robot does not exist
Cause: Orchestrator cannot match the machine's domain\username to a registered Robot, usually a wrong username in the Robot config or a different domain after a rename/migration.
Fix: Run 'whoami' on the Robot machine for the exact domain\username. In Orchestrator, update the Robot record's username to match exactly (Manage Access for Modern folders, or Folder > Robots for Classic). Verify the Machine Key matches Assistant > Preferences > Orchestrator Settings. Reconnect the Assistant.
Platform: UiPath
Category: config
Error: Robot Licensing Failed. There are no available licenses on the server. (#1914)
Error code: 1914
Cause: Orchestrator shows no free unattended licenses because duplicate machine entries are consuming slots without releasing them.
Fix: In Orchestrator > Tenant > Licenses, find duplicate machine entries holding unattended licenses and disable the duplicates, leaving only the correct machine active. If none, toggle the Robot type from Unattended to Attended and back to force a refresh. Re-trigger the job after the heartbeat cycle.
Platform: UiPath
Category: config
Error: Could not find an asset with this name. Error code: 1002
Error code: 1002
Cause: Get Asset/Get Credential cannot find the named asset because it is in a different Orchestrator folder than the process, or the Robot lacks read permission on that folder.
Fix: Confirm the asset name matches exactly (case-sensitive). Check which folder the asset lives in vs the process's folder. Set the activity's Folder Path property to the correct path (use / for nested). For shared folders, ensure the Robot account has Viewer or higher permission.
Platform: UiPath
Category: config
Error: Add Queue Item: Queue does not exist. Error code: 1002
Error code: 1002
Cause: The Add Queue Item activity references a queue name not in the Orchestrator folder the Robot runs under, often after a Classic-to-Modern folder migration.
Fix: Verify the queue exists in the expected folder. In Studio, set the activity's Orchestrator Folder Path to the exact folder where the queue is defined. Confirm the Robot account has permission to that folder. Republish after correcting folder settings.
Platform: UiPath
Category: connectivity
Error: No connection could be made because the target machine actively refused it
Cause: The Robot service (Service Mode) cannot reach the Orchestrator HTTPS endpoint because the machine uses an unconfigured proxy, or port 443 is firewall-blocked.
Fix: Verify the Orchestrator URL is reachable from the machine via a browser and that outbound 443 is open. If behind a proxy, add proxy settings to uipath.config under %ProgramFiles%\UiPath\Studio\. Restart the UiPath Robot Service, then reconnect from the Assistant.
Platform: UiPath
Category: version
Error: Cannot create unknown type '{http://schemas.uipath.com/workflow/activities}ReadRange'
Cause: The workflow references the ReadRange (or other Excel/Mail/PDF) activity but the corresponding activities package is missing or not deployed on the Robot machine.
Fix: In Studio, open Manage Packages and confirm UiPath.Excel.Activities is installed and current. When publishing, ensure dependent packages are in the Orchestrator NuGet feed or the Robot's local package folder. On the Robot, clear the .nuget cache (C:\Users\<user>\.nuget\packages) to force a fresh download. Re-run.
Platform: UiPath
Category: version
Error: Could not load file or assembly 'UiPath.System.Activities, Version=23.4.2.0'
Affected versions: 23.4.0
Cause: Studio 23.4.0 had a packaging defect where published .nupkg files listed incorrect runtime dependencies in the .nuspec, so the Robot fails to resolve UiPath.System.Activities at execution.
Fix: Downgrade Studio to 22.10.7 and republish. Or extract the .nupkg, correct the .nuspec dependency entries to the 22.10.7 format, repack, and re-upload. Add the UiPath Official NuGet feed to NuGet.config so the Robot can resolve packages. Upgrade past 23.4.0 once verified.
Platform: UiPath
Category: version
Error: RemoteException: Could not load file or assembly '{ProjectName}'. The system cannot find the file specified
Cause: The Robot machine runs an older UiPath version than the one used to publish, so it cannot resolve the project assembly or its dependencies from the NuGet cache.
Fix: Upgrade the Robot/Assistant to the same version used in Studio. Clear the Robot's NuGet cache (C:\Users\<account>\.nuget\packages) and re-trigger so dependencies re-download. If the package relies on custom libraries, ensure those .nupkg are in the Orchestrator feed. Confirm the process version points to the correct package.
Platform: UiPath
Category: config
Error: The type initializer for 'UiPath.NuGet.UiPathUtils' threw an exception
Cause: The NuGet.Config in the Windows system profile (used by the Robot service account) is missing or malformed, so the Robot cannot initialise its NuGet resolver at job start.
Fix: Go to C:\Windows\System32\config\systemprofile\AppData\Roaming\NuGet (or SysWOW64 for 32-bit). Verify NuGet.Config begins with a valid XML declaration. If absent or corrupt, copy a valid one from a user profile or recreate it with the correct feeds. Restart the UiPath Robot Service and re-run.
Platform: UiPath
Category: auth
Error: 535: 5.7.3 Authentication unsuccessful
Cause: UiPath.Mail.Activities above 1.9.5 changed SMTP password transmission to SecureString, rejected by mail servers that do not support secure auth on the configured port/TLS.
Fix: In Send SMTP Mail Message, try port 587 with SecureConnection 'Auto', or port 25 with 'None'. If using a credential asset, pass the plain-text password. Downgrade UiPath.Mail.Activities to 1.9.5 as a stable workaround, or upgrade to 1.12.2+. Ensure the mail server (Exchange/O365) allows Basic Auth or App Passwords.
Platform: UiPath
Category: auth
Error: You are not authenticated
Cause: The OAuth2 bearer token used for Orchestrator API calls (via HTTP Request or Start Job) has expired or was generated with incorrect client credentials.
Fix: Re-generate the access token from the identity token endpoint with valid client_id/client_secret from your Orchestrator External Application. Confirm grant_type 'client_credentials' and correct scope. In Swagger/Postman, click Authorize again. For long automations, refresh the token before its ~1-hour expiry.
Platform: UiPath
Category: version
Error: BusinessRuleException is ambiguous between UiPath.Framework.Activities and UiPath.Core
Cause: Both UiPath.System.Activities and an older UiPath.Framework.Activities are referenced, each exporting BusinessRuleException, causing an ambiguous-reference compile error in Throw activities.
Fix: In Manage Packages, remove the legacy UiPath.Framework.Activities if unused. In Throw/Catch activities, fully qualify the type as UiPath.Core.BusinessRuleException. Run Analyze Project to confirm no remaining ambiguity. Republish after clearing the old package.
Platform: UiPath
Category: other
Error: RemoteException: Job stopped with an unexpected exit code: 0xC0000005
Error code: 0xC0000005
Cause: An access-violation crash, most commonly from a version mismatch between the UiPath Excel activities package and the locally installed Microsoft Excel.
Fix: In Studio, open Manage Packages and downgrade UiPath.Excel.Activities to a version compatible with your Excel (e.g. 2.8.x to 2.5.x/2.6.x). Re-publish and re-run. If it persists, confirm antivirus/firewall is not blocking UiPath robot processes.
Platform: UiPath
Category: version
Error: XamlObjectWriterException: Cannot create unknown type (activity)
Cause: The Robot/Orchestrator runtime runs an older activity package that does not recognise activity types from the newer package used at development time.
Fix: Align Studio, Robot, and Orchestrator on compatible versions. In Studio's Manage Packages, downgrade UiPath.UIAutomation.Activities and UiPath.System.Activities to versions the Orchestrator supports, re-publish, and re-trigger. If already aligned, clear the Robot's NuGet cache (%userprofile%\.nuget\packages\) to force a fresh download.
Platform: UiPath
Category: schema
Error: The given key was not present in the dictionary
Cause: Code or a queue handler reads a dictionary/queue-item field by a key that does not exist at runtime — misspelled, wrong case, or never populated.
Fix: Guard access with ContainsKey (If: myDict.ContainsKey("KeyName")) and handle the missing case. Verify exact key names against the queue item schema. Wrap access in Try-Catch on KeyNotFoundException to log the missing key. For REFrameworks, confirm SpecificContent fields are populated before Process Transaction.
Platform: UiPath
Category: config
Error: Could not find file ...\.nuget\packages\...\Main.xaml
Cause: On non-persistent VDI/VM environments the robot's NuGet cache is wiped on logoff, so later Orchestrator-triggered runs cannot find the unpacked .xaml files.
Fix: Confirm by logging off and back on and checking the path. If the cache clears on logoff the image is non-persistent — have IT persist the profile or redirect the NuGet folder to a persistent drive. Short term, run the Robot service under a Windows service account to keep the cache alive. Verify project.json's 'main' points to Main.xaml.
Platform: Zapier
Category: other
Error: Response payload size exceeded maximum allowed payload size (6291556 bytes)
Error code: 6291556
Cause: The error "Response payload size exceeded maximum allowed payload size (6291556 bytes)" fires when a single Zap step receives more than ~6 MiB of data from the connected app or step
Platform: Zapier
Category: connectivity
Error: Trigger partner failure
Cause: The trigger app's API did not respond successfully within Zapier's polling window, due to an outage, quota, throttling, or auth issue on the partner side.
Fix: Wait for the next poll - Zapier retries and picks up missed records automatically. If it recurs, reconnect the app in the trigger step. Check the partner's status page. For persistent failures, simplify the trigger (fewer filter fields, smaller data sets).
Platform: Zapier
Category: schema
Error: Invalid API Response: Got a result missing the "id" property
Cause: Zapier's polling dedupe requires every object in a trigger's result array to include a top-level field named exactly 'id'; the API returned objects without one.
Fix: Switch the trigger to Code Mode and map an existing unique field to id, e.g. return results.map(r => ({ ...r, id: r.recordId })). If items are nested in an envelope, extract the array first. Or set a Deduplication Key in the trigger if the app supports it.
Platform: Zapier
Category: schema
Error: Invalid API Response: Results must be an array
Cause: A polling trigger expected a bare array of items but the API returned a wrapper object (e.g. {"items": [...]}) or undefined.
Fix: Switch the trigger to Code Mode and return just the array, e.g. return bundle.response.data.items. Always return an array even when empty (return [] not null). Re-test the trigger to confirm Zapier accepts the shape.
Platform: Zapier
Category: timeout
Error: Task timed out after 160 seconds
Cause: A Zap step (commonly a Google Sheets lookup/update) exceeded Zapier's 160-second limit, usually because the target sheet is too large or complex.
Fix: Trim unused rows, remove volatile formulas (ARRAYFORMULA, IMPORTRANGE), and archive old data. Use a simple indexed search column (ID/email, not a formula). Consider Zapier Tables or a more targeted API call instead of a large Find/Update. Replay the failed run after simplifying.
Platform: Zapier
Category: schema
Error: Invalid Syntax: Only numeric values are allowed
Cause: Formatter's Number transform received a value with non-numeric characters such as a currency symbol, comma, or a line-item array.
Fix: Add a Formatter > Text > Replace step before the math step to strip the offending characters. If the input is a line-item array, add Formatter > Line-items > Line-item to Text first to flatten it, then map the cleaned value into the Number transform.
Platform: Zapier
Category: schema
Error: Formatter error: Failed to create a number transform; the app returned "Invalid Syntax."
Cause: The Formatter Number transform received a value it cannot parse - an empty field, a text string, or mixed content from a prior step.
Fix: Open the failing run in history and inspect the exact value reaching the Formatter input. Add a Formatter > Text > Replace upstream to remove non-numeric characters. If the field is sometimes empty, add a Filter or Paths step to skip the Formatter when blank.