I have logs to monitor.
If an error message appears in log, I want trigger to be activated - it works fine.
Now, I want trigger to stay activated until someone sees the error, and it can take from 1 minute to several days.
I cannot use "count()" and want to avoid sending an email or something like this. I've tried to use count(LARGE_VALUE) - now triggers stay long enough, but cannot be deactivated and using "unacknowledged only" filter does not help, since acknowledged triggers do not repeat if an error happens again.
Same functionality can be achieved by some external monitoring, but I want to avoid this if possible.
I've also seen this issue, but hope there still is a way to solve my problem, since it seems pretty common.
Related
I followed this tutorial to implement push notifications in my web app, and while they work, they stop working very quickly. It seems to handle the first couple of notifications well, but after that, sometimes when less than five minutes has gone by, the subscription expires, according to my back-end. I get an error code of 410 from the push service which the tutorial says is meant to indicate that the subscription expired.
This is crazy, how can a subscription expire in less than five minutes? I searched up my issue and it seems no one else has had this problem, some even saying that subscriptions can last years!
I tried implementing an event listener in my service worker for the "pushsubscriptionchange" event, but according to Serginho's answer, Chrome did not implement that event as of 2019, and I don't think that's changed since then.
Oh, and while Chrome can handle the subscription (but only once/twice as explained above), Firefox doesn't even do anything. I feel like I'm going crazy. If I test the push subscription feature itself using this site, however, it works in Firefox! and Chrome! What are they doing that I'm not? They show the exact same code as the tutorial I linked above.
What even can I do at this point? I've considered perhaps creating an interval with setInterval() and just resubscribing the user every second or so, but I don't think that'll work.
Any help would be appreciated.
You absolutely need to handle the pushsubscriptionchange in your service worker. Otherwise when a subscription expires and is replaced with a new one you will lose it.
Chrome and most browsers actually trigger that event (I don't know where you read something different). I am sure that it is triggered because on our push service we receive thousands of hits per hour from that event.
Take a look at our service worker if you need inspiration on how to implement that event. Then on your server you simply replace the old subscription with the new one.
My ps4 is currently set to automatically update, but since about a week ago or so, it's required that i boot up in safe mode in order to do so, giving me error CE-30002-5 (needing safe mode to update). This is going to get really tedious turning on the system, finding out it needs a system update, shutting it down, booting back up into safemode, updating, and then letting it boot back up in standard mode. Is there a way to fix this somehow where it doesn't need safe mode to update?
From a quick google search:
https://www.playstation.com/en-ie/get-help/help-library/error-codes/ce-30002-5/
In my opinion, I feel that you are focussing on the wrong aspect of this. It seems you are focusing on the issue that this task will become tedious, and not on the issue that you should be focussing on - which is that your system is throwing an error (eg: Something is not right or broken) .
You've got an error code, and google is your friend. You'll get better help there than someone else doing your research for you.
I am using an On Form Submission trigger in a Google Sheet that I created. The problem that I am having is that there is a chance that the form could be submitted quicker than it takes to execute the code, so the first submission is interrupted.
Ideally, I would like it to complete the execution for the first submission, and as soon as it completes, begin on the second submission. Is this possible?
Two options.
LockService or deal with concurrency.
Others have begun investigating using Firebase as an alternative to the in-built LockService due to recent reliability issues.
Personally the latter option is my recommendation. i.e. Have your project cope with multiple entry points at uncontrollable times.
Good luck, I have been fighting for a good solution for over a year now (with my Choice Eliminator add-on). The problem is that Google process your script after the form is submitted, so there is no real way to prevent overlapping submissions.
Here is what I have found.
You can temporarly shut off the form from accepting answers: This was actually the best way I have found, but it tended to confuse the end-user, and they also potentially lost the info they filled out if they hit submit and it was closed. I also found that if there was any hiccup in the onFormSubmit function the form would stay closed until the owner re-opened it.
LockService. I tested this and it really didn't do anything to help with the overlapping submissions. It prevented my code from running twice, but then my code didn't run on the second submission.
I personally chose to remove everything and make the script run as fast as possible. With one exception, I grabbed the time the script started, and ended, then displayed the difference to the owner of the script so they at least knew how long there needed to be between submissions to not have an error.
I am a Google App Script user since last 2 years. I see here in India during peak time i.e during evening the 1 minute trigger is not firing at proper time. Is there any server side issue or there is some other issue. Saying about the worse case scenarios, today my script trigger has not been fired since past 2 hours. I have correctly done logging. No log is printed means it does not even go to that method. Can anybody tell me what might be the exact reason behind it.
It might be beneficial to show us the code behind your script, given that there is a method that is potentially being skipped over. Have there been no errors thrown to you via the Google Apps Script notifications?
It seems, perhaps, your issue may fall into place with this currently reported error: https://code.google.com/p/google-apps-script-issues/issues/detail?id=2708
We're likely not going to be able to give you a precise answer to your problem if we can't examine what you're currently working with. I wish you luck in your endeavor, though.
Well, I do hate asking vague questions but I can't help it this time:
Some macros I'm coding are taking a long time to run - and I just realized that it's incredible boring to just wait for it.
I want a progress bar. Or even a message box stating "Loading..." with a cancel button.
I tried using MS help to do this, but they require an ActiveX controller and that's just not an option.
Personally, I really didn't even try to code anything becouse I'm not even sure if it's possible! Everytime I open a MsgBox the whole program stops running, and that's not my idea.
I tried checking some concepts in C+ or Java, but most people seem to use a function just for that.
Anyway, any kind of lead or small piece of information would help a lot.
PS.: Yeah, I'm using Access 97, and that's not something I can change in the moment.
The problem with using MsgBox is that it stops everything until it gets a user response. That's not what you need for this.
Try making a very simple Wait form. It would have 1 unbounded label that says "Please Wait". Before your calculations begin, call it up with a docmd.OpenForm(... and close it when you're done with a docmd.closeform(...