How to troubleshoot "We couldn’t find a run python"? - python-3.x

I'm working on a pre-existing python code-by-zapier zap. The trigger is "Code By Zapier; Run Python". I've made some changes to the contained python script, and now when I go to test that step I run into the following error message:
We couldn’t find a run python
Create a new run python in your Code by Zapier account and test your trigger again.
Is there any way of figuring out what went wrong?

I'm guessing a little bit, but I think this issue stems from repeatedly testing an existing trigger without returning a new ID.
When you run a test (or click the "load more" button), then Zapier runs the trigger and looks through the array for any new items it hasn't seen before. It bases "newness" on whether it recognizes the id field in each returned object.
So if you're testing code that changed, but is returning objects with previously seen ids, then the editor will error saying that it can't find any new objects (the can't find new run pythons is a quirk of the way that text is generated; think of it as "can't find objects that we haven't seen before).
The best way to fix this depends on if you're returning an id and if you need it for something.
Your code can return a random id. This means every returned item will trigger a Zap every time, which may or may not be intended behavior.
You can probably copy your code, change the trigger app (to basically anything else), run a successful test (which will overwrite your old test data), and then change it back to Code by Zapier and paste your code. Then you should get a "fresh" test. Due to changes in the way sample data is stored, I'm not positive this works now
Duplicate the zap from the "My Zaps" page. The new one won't have any existing sample data, so you should be able to test normally.

Related

Blue Prism: Object not found when ran using Control Center, but runs without issue through Process Studio

During my process there is a drop-down html element that I have spied and set correctly. I run through the Object and Process studio without any issues. Once the same process is ran through the Control Room the element throws and error that it cannot be found.
I have tried multiple different configurations without any luck and the element is still found without issue when ran manually. I even checked by signing into the VM having it error and on the second retry had the VM up; at this stage the element was found without issue. It seems to only be when the bot is running and the screen is not up. No other elements give this issue and the next step is the same dropdown, but for a stop time not start.
Any help would be appreciated!
I have added pics of the STARTSPIED - START and ENDSPIED - END spied configs,the Navigation Stage, and the process correctly running in the Object Studio OB Studio correct.
Thank you!
For the person who down-voted this item...Configs here are my two days of config changes and research that I tried on my own before asking for help. This is my 5th automation that I have put into deployment without help, so thank you for down-voting someone trying to get help where they are stuck.
Your problem is most likely connected with the fact that processes run in the control room are executed much faster than in studio and your webpage might not be loaded on time (that would explain why it works after retry).
Best practice approach would be to add a dynamic wait stage after attach and use “Parent Document Loaded” option on the element you want to interact with. It will wait for the page to be loaded and then check exist for the element. I would also suggest splitting your action into two, first to set start date and second for end date.

UFT error: Cannot identify the object

I'm using Unified Functional Testing v12.02 (or QTP).
Sometimes while running script i get the below error and sometimes I don't.
Cannot identify the object "..." (of class ...) Verify that this
object's properties match an object currently displayed in your
application.
Tip: If the objects in your application have changed, the Maintenance
Run Mode can help you identify and update your steps and/or the
objects in your repository.
I checked OR and the object itself with Spy tool and they have the same properties.
Sometimes I get the same error in other objects, but if I run again the script it works well.
Can someone explain me what might be the problem?
Im a little bit confused why sometimes i get these errors and sometimes don't.
I'm testing a simple web application (for training purposes)
Also I'm using the following add-ins: Web, Web-SAPUI5, Visual Basic
Mostly object wont be in the readystate. Check State of the Object using
Webedit(googlesearch).object.readyState="complete"
Webedit(googlesearch).object.Load
Webedit(googlesearch).object.Disabled=False

Visual Studio SSRS - Define Query Parameters Window

A couple of months ago I created and published over 50 reports. Each report used a stored procedure that accepted parameters.
Now when I try to create a new report with a stored procedure VS doesn't want to play nice. Instead of reading the parameters and fields of the stored procedure and populating the corresponding tabs in the DataSet properties, I am now encounting a new window titled "Define Query Parameters".
I even went back tried creating a new report with an old stored procedure (that still works in my old report).
What's changed in VS? Why is it all of sudden prompting this new window and how do I make it go back to the previous behaviour?
This happens to me sometimes. I don't know exactly why, but it seems to have to do with Visual Studio needing some dummy parameter values so it can test your stored procedure and get a sample output so it knows what fields to expect. Maybe it tries some dummy values on its own and if they work it doesn't have to ask you, but if it doesn't, it has to ask you to provide them.
What I do know is that when I get that "Define Query Parameters" dialog box, if I just type in some valid dummy values and click Ok, it works fine, lets me finish building the dataset, and I can finish building the report in peace.
So to summarize: I don't exactly why, but this isn't a setting that changed in VS. The potential for it to happen has always been there, but it only happens sometimes, and you just have to deal with it and move on.

Open a dialog from a Sitecore uiUpload Pipeline process

I'm currently trying to show a SheerResponse.YesNoCancel() dialog within the Save uiUpload pipeline process from Sitecore. The problem appears when I do that call and it throws a NullException. I thought it was weird so I started copying the code from Sitecore's DLL and adding it to my solution. After that, I found that if the property OutputEnable is false it returns a ClientCommand that is NULL and when it tries to add a control to it, the Exception appears. So Fixing that I was able to finish the execution of that method. Anyway I still can't show the dialog. So the question is: Can I show a Dialog from a Sitecore uiUpload pipeline?
Have you tried using Sitecore.Context.ClientPage.ClientResponse.YesNoCancel(), i did something similar to what you are trying to do, but i used Alert(), worked fine for me.
Update: Actually inside uiUpload pipeline you can't call this method, however what you can do is use HttpContext.Current.Response.Write("<html><head><script type=\"text/Javascript\">[Your Java Script</script></head></html>"), you will need to abort the pipeline after this args.AbortPipeline();, not sure if this will help your case or not
No you cannot. From http://sdn.sitecore.net/Articles/Media/Prevent%20Files%20from%20Uploading.aspx:
The uiUpload pipeline is run not as part of the Sheer event, but as part of the form loading process in response to a post back. This is because the uploaded files are only available during the "real" post back, and not during a Sheer UI event. In this sense, the uiUpload pipeline has not been designed to provide UI.
That page was written for v5.1 and 5.2, but I'm pretty sure it still applies. The page claims that you can emit javascript to the page like Ahmed suggested, but it didn't work when I tried it.

InvokeWorkflowActivity doesn't call workflow

I'm trying to get one workflow to call another one. I tried using the invokeWorkflowActivity, I set the TargetWorkflow to the workflow that I want to get called. It's in another project so I added the project as a reference.
What else do I have to set up in order for this to work properly. I get no errors, the first workflow starts and then completes as expected because the call to start the workflow is asyncronous. The problem is that my second workflow doesn't seem like it's getting called.
Thanks.
try this sample..
http://blogs.msdn.com/sdanie/archive/2006/06/23/644366.aspx
this may help you

Resources