Failed to verify ________. Connection errors and how to handle them

How To
,
1

I regularly run into “Failed to verify __________” (fill in the blank with account, connection, or other similar word) initialization errors that occur before a scenario starts. It happens with all types of modules, QuickBooks, Google Sheets, Asana, etc. At the time of the error, the scenario is usually stopped and needs to be manually turned back on.

Under normal circumstances I would apply error handlers that would pause, ignore, etc. but there is no option to do so when the scenario does not start to begin with. It just fails and stops.

Is there a way to treat these special cases that circumvent normal error handlers? Some people have suggested creating a scenario to monitor the state of other scenarios, but I haven’t been able to find information on how to build those out. This becomes a bigger issue when I am not present to turn the scenarios back on.

I appreciate any feedback. Thanks.

image
image1920×1040 181 KB

1 Like
3

Hi,

I know there are these settings in your Make profile:

image
image1520×376 28.4 KB

Does that help? If email isn’t your preferred method, you could always have some automation running that sends you a texte message or something when it sees one of these errero messages in your email. Of course if that one fails.…

L

4

Hello,

Yes, I receive notifications when a scenario stops, and it is helpful being notified that I need to a investigate and turn a scenario back on.

I’m looking for a solution to prevent them from turning off altogether, or have a system to monitor and automatically turn them back on. In most cases, the scenario will run as intended shortly after failure when they are turned back on.