Hello. Let me explain. I made a scenario that checks my Google Calendar every day to send an SMS to the customers of the day. But some days there are no customers. So on days when there are no customers the scenario marks an error because no SMS is sent. How can I avoid this because it puts my scenario on hold? Thanks in advance. I think you have to use the commit function but when I want to use it it says non-configurable.
blueprint.json (38.8 KB)
I don’t see any Google Calendar or SMS modules in your scenario.
If you need further assistance, please provide the following:
1. Relevant Screenshots
Please share screenshots of your scenario, any error messages, relevant module fields, and filters in question? It would really help other community members to see what you’re looking at.
You can upload images here using the Upload icon in the text editor:
2. Scenario Blueprint
Please export the scenario blueprint file to allow others to view the mapped variables in the module fields. At the bottom of the scenario editor, you can click on the three dots to find the Export Blueprint menu item.
3. Output Bundles of Modules
Please provide the output bundles of the modules by running the scenario (or get from the scenario History tab), then click the white speech bubble on the top-right of each module and select “Download input/output bundles”.
A. Upload as Text File
Save each bundle contents in your text editor as a bundle.txt file, and upload it here into this discussion thread.
B. Insert as Formatted Code Block
If you are unable to upload files on this forum, alternatively you can paste the formatted bundles.
These are the two ways to format text so that it won’t be modified by the forum:
-
Method 1: Type code block manually
Add three backticks
```before and after the content/bundle, like this:```
content goes here
``` -
Method 2. Highlight and click the format button in the editor
Providing the input/output bundles will allow others to replicate what is going on in the scenario even if they do not use the external service.
Following these steps will allow others to assist you here. Thanks!
Handle errors so scenarios don’t stop.
You might want to add some error handling to your modules to handle exceptions, so the failing module(s) can automatically be retried or ignored. By handling any errors by adding a “Error handler” to the module, the scenario won’t throw an error and get turned off.
Error directives can only be added to an error handler route.
1. Right click and select “Add error handler”
2. Error handlers will appear
For more information on error handling, see:
- Introduction to errors and warnings in Make
- Overview of error handling in Make
- Error handlers
- Overview of error handling in Make
- Watch these videos by Make - Learn all about error handling (YouTube playlist)
- Webhook Error Handling
- Types of Errors (including RateLimitError HTTP 429: too many requests)
Hope this helps! Let me know if there are any further questions or issues.
— @samliew
P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.
hi here the scenario
blueprint.json (31.4 KB)
Thanks a lot !!! that’s work