I have google apps of form, when response save in spreadsheet, it activate a script to send an email to a user. After running 4 months, today I got an error message through script response:
Details:
Start Function Error Message Trigger End
11/10/16 10:49 AM formSubmitReply Authorization is required to perform that action. formSubmit 11/10/16 10:49 AM
I checked "Connected apps & sites" of "sign-in & security" of "My Account" in google. It registers 7 my apps but not the error apps.
So, I want to ask how I can activate the missing apps in authorization list.
Thanks in advance.
I had this one yesterday. I opened the faulty script in the script editor and executed it with the Run (play button) command. Don't forget to choose the function name in the drop down list on the right or it will be greyed out.
Then it asked for permissions, after granted everything was alright again.
Related
I have created an Azure Logic App in the Azure portal and successfully added several steps. I add the Azure DevOps List Iterations step and click the sign-in button. A popup prompts me to sign-in and then closes and I am left with the follow error in the Logic Apps designer:
Failed with error: 'The browser is closed.'. Please sign in again.
I have am recreating a workflow that I originally created using Microsoft Power Automate (Flow) so I know that my credentials should work.
Now when I hit the sign-in again I do not get the option to re-enter any credentials nor change accounts.
What fixed it for me was allowing 3rd party cookies:
In your browser settings, make sure that you allow all cookies (including 3rd party cookies: a lot of Microsoft webapps depend on that),
Refresh the Logic App page (might not be required, but it doesn't hurt),
Add a new connection and sign in.
You can then block 3rd party cookies again after this if you wish.
for me change browser from Chrome to MS Edge beta helped
For this problem, please check the resource group which your logic app belongs to. When you click the "Sign in" first time, it will generate a "API Connection" in the same resource group of you logic app. Its name should be like "visualstudioteamservices" (shown as below screenshot).
Please delete this api connection and then wait a few minutes(because there may be a delay in deleting operation). Then go back to your logic app and delete the DevOps List Iterations action, then create the DevOps List Iterations action again it will ask you for the sign in credential.
By the way, if your browser remember the last credential, it may still have some problem. Please delete the api connection and change to another browser to have a try.
Open an incognito/private window in your browser, then attempt to create the connection.
Just had the exact same issue, thought it had to do with my subscription being free trial.
But it logged in perfectly once I switched from Safari to Chrome (on a MacOS 11.2).
I had the same problem using Firefox to create a Logic App, solved by turning off Enhanced Tracking Protection for portal.azure.com
My test invocation name is "Mrs Tang", so i input "Talk to Mrs Tang", but it responds "Sorry, this action is not available in simulation"...
Does anybody know How can I resolve this error?
According to the doc:
Turn on the Web & App Activity, Device Information, and Voice & Audio
Activity permissions on the Activity controls page for your Google
account. You need to do this to use the Actions Simulator, which lets
you test your actions on the web without a hardware device.
And I had do what Jeremy Gordon suggested. To add a second google account in the GCP IAM console with a viewer action permission and then login with this second google account in an incognito window for the web simulator to work.
I had a related problem (I could test with my main developer account, but not my test credentials). I eventually got it working with the non-primary account.
The missing link for me was that when I was viewing the simulator, I was actually signed in to two accounts, my primary google account (developer account, shows up in the main frame of the page, upper right corner), and the account I authorized when 'starting' the simulator (email address shows up in the simulator frame), which was my test credentials. The second test account repeatedly gave me the "Sorry, this action is not supported in simulation" message, until I:
1) Added the test account as a Conversation API Viewer & Client in GCP IAM console
2) Visited the 'create link' (the one that comes up when you click share) in an incognito window, and signed into the secondary account there such that I was signed into only one account in that incognito window.
After that, invocations connected to the app.
Make sure you are logged into the same account you used to deploy the test action and that the deployment has been done within the past half hour or so. If you have not set all the information on the Actions on Google Console, you may need to use the invocation phrase "Talk to my test app".
I think sometimes I run into the same error. I get past it by toggling the Active switch off and on.
Same problem I encountered. You must be logged in via the secondary google account. Do logout from the account and login via the account that is paired with api.ai.
why I can't use google action in web simulator
I got this to work by saying "talk to my test app" or typing it in to the simulator prompt, that triggered my app to start in the simulator.
I had the same problem. I needed to set the location first (it defaults to Google-Headquaters), if you are in some other region (like in germany as i am).
Then go on with "Mit meiner Test-App sprechen" (Talk to my test app), or whatever it is in your language!
I did not get this message on my invocation, but on my my second input:"Sorry, this action is not available for your app.".
It turns out the simulator had left the conversation right after the invocation (and it did mention that in the small print).
This happened because I returned a FinalResponse for the invocation. And a final response is pretty final, it will terminate your conversation.
So, after a FinalResponse you can only get back in your action/conversation by a new invocation or a deep link. If you want to suggest questions/inputs, then you should return ExpectedInputs.
You might need to turn on Web & App Activity to let group members use some Google Assistant features.(if you are using organizational account)
https://support.google.com/assistant/answer/7219584?hl=en
If you are using any organization's Google Accounts then there might be an access issue. So use your own personal Gmail account.
Take a look here, organization's might not be given you access. So use your personal Gmail and follow the Docs, you will able to create your agent/ actions and able to test it with simulator as well as in android device.
At time of testing the Google Action you need to set the location to the country which you selected while developing or submitting your Google Action.
By default US is selected in testing but if your action is for one particular country only then you need to select that. You can see in image the field where you can select location
I tried to build the Paypal Express Checkout. Last week all runs smoothly, I can create REST API app and the sandbox account as well.
But today, All the details is removed.
And there is this warning
We’re sorry, but something went wrong while getting your credentials.
Please try again.
When I tried to create a new app/new sandbox account it says
We're sorry, something went wrong during account creation. Please try
again.
After some googling and trying some of the solutions like "password is too weak", I realise that all the solutions are from years ago and all the screenshot is the old PayPal interface.
I would assume that this is related to the new PayPal.
PS: I am from Australia and have read the "Non-US developers should read our FAQ"
Anyone know how should I create REST API App?
This is not the correct way to create the API, but this resolves my problem instantly.
I had the same problem. The "Sandbox developer account" dropdown box had no entries although I had set up accounts before - so I couldn't create an app. After some trial and error hacking I finally found a way to inject a valid option in the html select and successfully created the app in the end.
Here's how:
Log in to your developer.paypal.com profile and go to Sandbox - Accounts.
Just use Firebug in Firefox or Developer Tools in Chrome to examine the source: Check the source of your BUSINESS account and you will find a code line like this:
<a class="profile" target="/developer/accounts/detail/22971020450123198612">Profile</a>
Note the id (e.g. 22971020450123198612), the country code (e.g. GB) and the email address.
Now go to Dashboard - My Apps & Credentials and press "Create app"
Open Firebug/Dev. Tools and examine the "Sandbox developer account" dropdown box. Right-Click the empty select in the dom and choose "Edit as HTML". Enter an option tag with your formerly noted values, just like this:
<option value="2297102045097598612,email#domain.com">email#domain.com (US)</option>
Check that the option now appears in the dropdown box.
Enter a name in the "App name" field and press "Create app".
That's it. Hope I could help.
I've signed in to the developer website but when I go to the apps page to create my app I see the following error message:
Problem creating sandbox facilitator account [Error code: 2001]
When I look on the sandbox accounts page I see there is a facilitator account there (xxx-facilitator#xxxx.xxx)
When I click the "create app" button the "sandbox developer account" dropdown is empty and when I try to create an app I get the following error message:
We’re sorry, but something went wrong while creating the application. Please try again.
So far I've:
created new sandbox users
submitted a query to paypal's tech support (no response)
left it a day and tried again
logged in, logged out...
I had the same problem. The "Sandbox developer account" dropdown box had no entries although I had set up accounts before - so I couldn't create an app.
After some trial and error hacking I finally found a way to inject a valid option in the html select and successfully created the app in the end.
Here's how:
Log in to your developer.paypal.com profile and go to Sandbox - Accounts.
Just use Firebug in Firefox or Developer Tools in Chrome to examine the source: Check the source of your BUSINESS account and you will find a code line like this:
<a class="profile" target="/developer/accounts/detail/2297102045097598612">Profile</a>
Note the id (e.g. 2297102045097598612), the country code (e.g. US) and the email address.
Now go to Dashboard - My Apps & Credentials and press "Create app"
Open Firebug/Dev. Tools and examine the "Sandbox developer account" dropdown box. Right-Click the empty select in the dom and choose "Edit as HTML". Enter an option tag with your formerly noted values, just like this:
<option value="2297102045097598612,email#domain.com">email#domain.com (US)</option>
Check that the option now appears in the dropdown box.
Enter a name in the "App name" field and press "Create app".
That's it. Hope I could help.
I got the 'Problem creating sandbox facilitator account' error as well but it was with a different error code of 'TAGETLIST404-20141017053750'. Obviously the suffix is just a timestamp.
The problem seemed to have been caused by the Oauth login popup that initially returned a timeouted session error but appeared to have still logged in anyway as it showed my name in the topright corner. But trying to create new apps returned the sandbox facilitator error.
Clearing cookies and logging in again, not getting the timeout error seemed to fix it and I could create accounts. I know this isn't a great answer but it's something to try.
I waited two days, and the error messages regarding the facilitator account went away. I was then able to make a new business account. This then allowed me to create a REST app without error.
I had the same problem and fixed it by just editing the source a bit.
Right click on the dropdown for your account if it's empty and click on Inspect element in your browser.
Inside the tags for the dropdown, add your email in tags. The email should be of a valid sandbox account that you had created.
For example, if you'd like to add a sandbox account with the email business#example.com,
add business#example.com within the select tags.
Seems like it's something easily fixable from Paypal's side but they haven't bothered fixing it yet.
for PayFlow API - allow up to 3 hours for the change to go into effect.after 3 hours it saved data while clicking.
In my case my primary email account was not confirm. after confirm it allow me
Today, I've just encoutered the same error with you. The problem is how Paypal raise the error, which made us very confuse. The error they should raise is: " You have not created any developer account yet, create an account and try again".
And here is how I fix it:
Go to: https://developer.paypal.com/developer/accounts
Create a BUSINESS sandbox account.
Go back and try create app again to see if it work.
A program I wrote crashes on startup. (Win XP).
A dialog "Please tell Microsoft about this problem." appears. I want to be told about the problem since it's my app.
Thing is, clicking through (clicking link: 'View the contents of the error report'), the "Error Report Contents" dialog doesn't let my customers copy its contents to the clipboard.
Do you know how a user can get a copy of this report to forward to me, the developer?
Don't worry. The developers can subscribe to WinQual. Microsoft will then forward the error reports to them.
Windows Error Reporting is part of Microsoft's Winqual service.
Sign up at the Winqual web site. Instead of just using a username/password to log in, you'll need to purchase an SSL certificate to identify yourself and your organization. This costs $99 if you only need the cert for identification purposes. If you also want to use it to sign code, it's $499.
Run the Microsoft Product Feedback Mapping Tool (available from the Winqual site) on a local copy of your application, and submit the results to the Winqual web site. This registers your application with Winqual.
From this point forward, any errors reported via Windows Error Reporting against your submitted applications are available to you if you log in to Winqual.
Use Alt-printscreen that grabs a copy of the active window, then paste it into word or something.