Your script, Copy of Send SMS - Techawakening.org, has recently failed to finish successfully. A summary of the failure(s) is shown below. To configure the triggers for this script, or change your setting for receiving future failure notifications, click here.
The script is used by the document Copy of Get Free SMS alerts for New Incoming Emails on Gmail - Techawakening.org.
Summary:
Error Message Count
Authorization is required to perform that action. 1024
I have received email like this
Do i have to authorize every time?
You have to (re-)authorize every time when you change the script. If you don't touch it, then the authorization will be saved and the set-up triggers run properly.
Related
The office365 trigger when new -email arrives (V3) is my logic Appp trigger condition.
The workflow does following:
Triggered on incomnig e-mails
check if sender is an AD User, if not send to a special Mailaddress
analyse the subject and put informations gother in new mailboydies and
distribute the mail to other mailboxes
I have seen a few cases I don' t understand, what it is the reason for that.
I got a trigger sicceeded but the trigger doe not fired Why?
image1: trigger History
image 2: not Fired Triggers
Screenshot shows succeeded triggers but not fired to start a run.
In this time spawn there was no email in the inbox.
I got a trigger failed ( i cannot reconstruct which mail could the reason).
image3: failed Trigger
for this case I can say nothing i found no e-mail at this time,
but it is possible that there was through Dectivation/Activation of logic app
old not readed mails ttries to trigger.
it was the first trigger after creation of this Logic app for testing
(copied from other subscription).
Can someone say me possible reasons for this 2 situations?
A status of skipped just indicates that the nothing new was found to fire the logic. Because the trigger will do check operation every once in a while even though the mailbox do not receive new email.
I think you do not need to worry about the records under "Trigger history". You just need to check the records under "Runs history". The records under "Runs history" can give a more intuitive picture of what's your logic app going on.
Email logs only if there was an exception at any point in the run.
I only want this for a specific robot, not all robots under management console.
I know there is an option under management console, but that emails for every robot and every log.I don't want that. Thanks
Add a try step as the very first action of your robot. At the lower branch, add any action to log your error (write file, send email):
Configure each action that may fail as follows:
The special robot property Robot.executionErros will hold the relevant error message. Here's an example:
That being said, I would rather rely on Kofax RPA's logging capabilities - any error gets logged to the logging database. You can then use another robot to get those entries and email send messages. This allows you to use a single robot for sending out email notifications instead of adding above steps to each one of them.
I'm getting a daily email from apps-scripts-notifications#google.com stating that
Your script, Email Studio, has recently failed to finish successfully. A summary of the failure(s) is shown below. To configure the triggers for this script, or change your setting for receiving future failure notifications, click here.
I have no idea what this is, but it lists 24 errors (see below) every day. Any advice as to what the problem is, what I should do about it and how to stop the daily email alerts would be much appreciated.
Summary:
Error Message Count
Authorization is required to perform that action. 24
Start Function Error Message Trigger End
9/21/18 3:13 AM triggerEmailStudio Authorization is required to perform that action. time-based 9/21/18 3:13 AM
9/21/18 4:13 AM triggerEmailStudio Authorization is required to perform that action. time-based 9/21/18 4:13 AM
Etc etc...
Sincerely,
Google Apps Script
I had the same issue with specifically Email Studio. Going to https://www.google.com/script/start/, choosing Edit, and "All your triggers", allows you to delete the Email Studio trigger.
I am trying to get the current location of the user and I am using the Api.AI web tool to create my actions/intent.
Deployed using -
firebase --only functions
API.AI Action -
Simulator -
Full index.js - link
But when my action is triggered I get this message -
Sorry, this action is not available in simulation
Can't we ask for permission on a simulation ? Also how do I test my app on a real device ?
EDIT:
The permission function is stuck in a loop -
Your problem is in this block of code:
//Action business logic
function welcomeMessage(app){
app.tell('Welcome !, Do you want to book a ride ?'); // Todo: Insert proper messages.
}
The app.tell() method sends the message and then closes the conversation. If you want to send the message to the user and keep the conversation going (ie - you're expecting a response) you need to use app.ask().
This is what is causing the "Sorry" message when you reply "Yeah" - your Action is no longer listening.
You can ask for permission in the simulation.
Once you have run it once in the simulator, you should be able to access it on any device that is linked to the same account you used to develop the Action, or to other accounts you've permitted (once they have run the simulator).
In our design we have something of a paradox. We have a database of projects. Each project has a status. We have a REST api to change a project from “Ready” status to “Cleanup” status. Two things must happen.
update the status in the database
send out an email to the approvers
Currently RESTful api does 1, and if that is successful, do 2.
But sometimes the email fails to send. But since (1) is already committed, it is not possible to rollback.
I don't want to send the email prior to commit, because I want to make sure the commit is successful before sending the email.
I thought about undoing step 1, but that is very hard. The status change involves adding new records to the history table, so I need to delete them. And if another person make other changes concurrently, the undo might get messed up.
So what can I do? If (2) fails, should I return “200 OK” to the client?
Seems like the best option is to return “500 Server Error” with error message that says “The project status was changed. However, sending the email to the approvers failed. Please take appropriate action.”
Perhaps I should not try to do 1 + 2 in a single operation? But that just puts the burden on the client, which is worse!
Just some random thoughts:
You can have a notification sent status flag along with a datetime of submission. When an email is successful then it flips, if not then it stays. When changes are submitted then your code iterates through ALL unsent notifications and tries to send. No idea what backend db you are suing but I believe many have the functionality to send emails as well. You could have a scheduled Job (SQL Server Agent for MSSQL) that runs hourly and tries to send if the datetime of the submission is lapsed a certain amount or starts setting off alarms if it fails as well.
If ti is that insanely important then maybe you could integrate a third party service such as sendgrid to run as a backup sending mech. That of course would be more $$ though...
Traditionally I've always separated functions like this into a backend worker process that handles this kind of administrative tasking stuff across many different applications. Some notifications get sent out every morning. Some get sent out every 15 minutes. Some are weekly summaries. If I run into a crash and burn then I light up the event log and we are (lucky/unlucky) enough to have server monitoring tools that alert us on specified application events.