I have a blueprism process which attaches to a web page and performs various actions. The process has been running smoothly for six months, but I am now getting an initial error of "ERROR: Internal : AMI error occurred in WaitStart Stage 'Wait For Detail' on page 'Update Claim' - External AppMan reader thread exited before response from query"
After this Blueprism is unable to perform any online action. I get a message saying that the "Read Thread Is No Longer Alive"
It appears to be caused by the Accessibility and UI identification methods in the App Modeller.
Issue was caused by Microsoft pushing out an update to Sharepoint.
Blueprism are aware of the issue and have put a post up notifying users https://help.blueprism.com/Automation-Design/Application-Integration/Active-Accessibility-Spy-Mode/1280268672/Why-does-Active-Accessibility-crash-Blue-Prism-when-spying-SharePoint.htm
I re-engineered logic to use HTML elements. I found that the focus action performed the same as a global mouse click center.
Related
Previously "Auto-preview" option was coming in dialog flow under integration section as shown in this below image , but Google discontinued this option from 14 April 2021.
https://cloud.google.com/dialogflow/docs/release-notes#April_14_2021
It seems that auto-preview option earlier was responsible for propagate changes of dialog flow to actions, and it reflects in Google Actions' testing simulator.
After removing "Auto-Preview", Is there any alternative way they provided to refresh content?
I am struggling with one issue currently, after making changes in dialog flow text response and saving it, doesn't reflect on Google Actions' test simulator.
I found that described issue of, "changes on dialog flow is not updating Google Actions's simulator" encountered because of error occurred in dialog flow, which is showing on click of "Test" button, that's error resulted into, not updating google actions's simulator.
Errors in 'DoorStatus' intent:
IntentDoorStatus has more than 128 training phrases. Reduce the number of training phrases to 10 or remove the intent from Implicit invocation.
com.google.dialogflow.designtime.exceptions.DesigntimeException: <eye3 title='FAILED_PRECONDITION'/> generic::FAILED_PRECONDITION: Errors in 'DoorStatus' intent:
IntentDoorStatus has more than 128 training phrases. Reduce the number of training phrases to 10 or remove the intent from Implicit invocation.
So, just to check I tried by removing some of the implicit invocation intents(e.g DoorStatus, DoorOpen etc.), those generating errors and tried testing without those intents. This time, it has updated the Actions successfully and now changed text response in dialog flow is reflecting on simulator.
Needs to improve:
In current flow, on click of the "Test" button (Inside Dialog Flow's Integration section), dialog flow navigates to Google Actions simulator regardless of error occurred in dialog flow. Dialog flow is showing the error in case it occurs, but since dialog flow redirects to simulator although error occurred, it seems that to developer as the changes which they did, will be reflected on simulator, but actually those changes won't reflect in simulator due to dialog flow error.
In this case of error in dialog flow, dialog flow should not redirect to Google Actions simulator. It should only allow to navigate to google actions' simulator, when dialog flow part builds successfully without any error. By preventing to navigate on simulator in case of dialog flow error , will help developer to aware about any occurred dialog flow error and provide hint to fix that error first before testing on simulator.
I want to fill a registration form by fetching data from excel using blueprism. In registration form the form redirects to another page after submission. But I am not able to do this flow in Process studio.
I Launched the Url and gave Loop start. The first data in excel is submitted but while fetching the second data from excel it throws an error message displaying
Application already launched
This is the Url "http://nancysara.wufoo.com/forms/z1c5ojru1qfibiq"
This error message happens when you are trying to use the Attach stage on an object that is already attached. You should have a logic in your object that checks whether attaching is necessary. Something like this:
This error occurs when trying to attach the Application or Browser that is being already attached to the Blueprism Object.
You can use "Read stage" to check the Application is connected or not.
Code looks like Code Block to check application connection
And read stage will be as below,
Read Block
You can create this code in new page and call this page before doing any interaction with the application
We have a document library hosted in Sharepoint Online with a single stage workflow attached that simply logs a few things and calls a web service. The workflow is triggered automatically when an item is updated.
The issue that we're having is that the documents are openned and changed in Word Online, which streams changes back to Sharepoint as they are made. This triggers the update event, but the document is still locked in Word Online so Sharepoint cannot even read the document metadata and the workflow hangs as a result. I need access to this metadata to pass to the web service.
The error is as follows:
Retrying last request. Next attempt scheduled in less than one minute. Details of last request: HTTP 423 to https://******.sharepoint.com/sites/etc/etc
The file "https://******.sharepoint.com/sites/test/Documents/test12311.docx" is locked for shared use by .
...and the action that it hangs on is:
Log The file [%Current Item:ID%] has bee... to the workflow history list
Once the browser tab is closed the lock is removed and the workflow completes.
Is what I'm trying to do even possible?
We have been getting an error prompt/alert in our XPages application at random times:
"An error occurred while updating some of the page...status:12152" and
"An error occurred while updating some of the page...status:12029"
We can't seem to pin it down to anything. Maybe someone has an idea of what these errors are referring to or maybe how to track it back to something? Thanks.
The HTTP 12152 error usually points to a network connection issue rather than anything specific to the browser or the Domino server.12029 again is down to an inability to make a connection to the server.
It sounds like the network connection is intermittent. I don't know what tools there are to test that, but I would suggest confirming you have a good, stable network connection between PC and server and that it's not getting negatively impacted by a firewall.
It looks like your application is trying to partially refresh content on the screen, and that this partial refresh fails. This can be because the component with that id is no longer found in the component tree.
Have a look at your XPages source code for controls with an id of MainContent and refreshPanel3 and find any partial refreshes on those controls. Check the rendered/loaded property for these controls to see if they are hidden in certain cases. If you do not render a control and want to display it using a partial refresh, you must partially refresh an outer component that contains the non-rendered control.
Use browser's network debug (F12 in Chrome/IE/Firefox w Firebug) to get real server response, it usually contains error page with more info. Failed partial refresh should be the last POST request.
I'm getting a weird threading issue inside a SharePoint workflow that I'd like to learn more about. I'm trying to send an email using SPUtility.SendEmail asynchronously by firing up a new thread to do it. This successfully works at the end of a workflow for a summary email. I tried doing the same to replace a task notification email but ended up receiving the following error:
Microsoft.SharePoint.SPException:
Attempted to make calls on more than
one thread in single threaded mode.
The only difference I can think of is that the task is inside a replication activity so it can create several of these tasks (although testing this it's only creating just the one). What specifically is the replication activity doing behind the scenes that might cause this error when I try to spawn a new thread?
[NOTE]
The reason I'm using threads to send the emails is because SPUtility.SendEmail is a blocking call, and in the case of a slow SMTP server the user might be getting their page back for up to a minute. And the reason I'm sending emails in the first place is because the standard task emails suck big time.
SPUtility.SendEmail uses an SPWeb parameter which is NOT thread-safe. SPSite, SPWeb objects are actually thread-specific so you shouldn't pass them from one thread to another. You should pass the site ID and web URL to the new thread and recreate the SPWeb object there.