노퇴근

an error handler is a way to handle errors when they occur during the execution of a Make.com scenario. you can use error handlers to make your scenarios more reliable and flexible.

there are five types of error handlers, and you can set their behavior based on what happens. for example, if you’re autopublishing to Twitter or Blogger and an error occurs due to the API, you can use an error handler.

first, see the photo below, and in the scenario status, if an error occurs in the module, you can use add error handler to add an error handler

option	role	usage
Break	breaks the scenario immediately	abort execution when an error occurs in a data-integrity-critical operation.
Commit	complete previous work, abort post-error work	when you need to preserve the results of work before the error.
Ignore	ignore the error and run the next action	when designing so that when an error occurs, it does not affect the workflow as a whole.
Resume	retry when an error occurs	when a transient error is likely to have occurred.
Rollback	cancel all actions and restore to original state	when the operation is transaction-based and the entire operation needs to be canceled in the event of an error.

1. Break

1. role
   • stops running the scenario immediately when an error occurs.
   • any tasks that were running are terminated, and no further progress is made at the point where the error occurred.

• usage situations
  • when a scenario can no longer run due to afatal error.
  • when data integrity is critical and you need to stop execution when an error occurs
    • example: stopping execution when an error occurs in a financial transaction, database update, etc.

• example
  • aborting a scenario when an error occurs while updating customer order data to prevent saving incorrect data.

2. Commit

• role
  • any actions executed before the error occurs will **complete (commit) normally**.
  • no actions are executed after the error occurs, and previous actions are preserved.

• usage situations
  • when you need to preserve the work done in the previous step.
  • when you need to ensure that successfully processed data is saved even if an error occurs
    • example: If an error occurs in a database update after sending an email, the email remains intact.

• example
  • if an error occurs in saving to the database after sending a customer email, but the email action that has already been sent is retained.

3. Ignore

• role
  • ignores the error and continues to run the scenario.
  • skip the action where the error occurred, and run the next action.

• use situation
  • when you need to continue running the remaining tasks regardless of whether an error occurs.
  • when the entire workflow should not be affected if an error occurs in a non-essential task
    • example: if an error occurs in a log save task, the main process should still run.

• example
  • keeping posts uploaded to other platforms even if an error occurs on some platforms while uploading posts to social media.

4. Resume

• role
  • retriesthe module where the error occurred.
  • retries after waiting a certain amount of time or until the error condition is resolved, which can be repeated a set number of times.

• usage situations
  • when an error is likely caused by a transient issue (e.g., network error, API limitations).
  • can be used in actions where retries are valid
    • example: Retry after a while when an API request fails.

• example
  • when a single network error occurs while sending data to an external API, but retrying is likely to succeed.

you can read more about how to use resume in this article.

https://xn--6i0b29d222b.com/2025/01/24/make-%ec%98%a4%eb%a5%98%ec%b2%98%eb%a6%ac%ea%b8%b0-error-handler-resume-%ec%82%ac%ec%9a%a9%eb%b0%a9%eb%b2%95/

5. Rollback

• role
  • undo **revert** to the state before the error occurred.
  • any actions that have already been executed will also be canceled, returning to the original state.

• usage situations
  • when you need to ensure data integrity in transaction-based operations.
  • when previously processed actions need to be canceled in the event of an error
    • example: canceling the entire transfer if some steps in a bank transfer fail.

• example
  • rolling back payment data already reflected in the customer’s account if an error occurs while updating object payment information.

summary cleanup

option	role	usage
Break	abort the scenario immediately	abort execution when an error occurs in a data-integrity-critical operation.
Commit	complete previous work, abort post-error work	when you need to preserve the results of work before the error.
Ignore	ignore the error and run the next action	when designing so that an error does not affect the workflow as a whole.
Resume	retry when an error occurs	when a transient error is likely to have occurred.
Rollback	cancel all actions and restore to original state	when an operation is transaction-based and you need to cancel the entire operation in the event of an error.

additional tips

• When setting uperror handlers, consider the importance of the task and the integrity of your data.
• set it up to keep alog recordso that when an error occurs, you can determine the exact cause.

each of the error handling options can also be used in combination for different purposes.

TheResume option is the ability to perform a retry on an operation that has encountered an error. When using Make.com, this is useful when a module encounters a transient error and the problem is likely to be resolved automatically. resume allows you to recover from the error and keep your workflow moving forward.

What does Resume do?

• retriesthe module (action) that encountered an error based on specified conditions.
• this is especially useful for recoverable errors, such as network delays, exceeding API limits, and temporary failures.
• executes based on the set number of retries and retry interval.

When to use Resume

1. when there is a possibility of resolving a transient issue
   • Response delay or throttling issues when making API calls.
   • external server connection failures.
   • temporary network errors.
2. when retrying is likely to recover from the error
   • for example, when an external API temporarily fails to return data, but is likely to succeed after a few seconds.
3. when automating long-running tasks
   • when trying to handle intermittent errors in a large data synchronization operation.

To set upResume

1. add an error handler

1. On the Edit Make.com scenario screen, hover over Modules.
2. click theAdd error handler button.
3. under Error handler, select the Resume option.

2. set retry conditions

When setting up theResume option, you can adjust the following conditions

• number of retries (Retries)
  • set how many times to retry when an error occurs.
  • example: 3 times.
• retry interval (Interval)
  • set the retry interval in seconds.
  • example: Retry every 5 seconds.

3. add retry conditions (Optional)

• you can set whether to retry based on specific error codes or messages
  • example: Retry only on HTTP 503 errors.

Examples of using Resume

example 1: External API calls

• scenario: Sending data to an external API.
• problem: HTTP 503 (Service Unavailable ) error due to network connectivity issues.
• solution
  • UsingResume, set up 3 retries at 5 second intervals.
  • if successful on the 3rd attempt, the workflow continues as normal.

example 2: Sending emails

• scenario: Sending an email through an SMTP server.
• problem: The server is temporarily busy or unresponsive.
• solution
  • UseResumeto retry twice, 10 seconds apart.
  • if retries fail, log an error or move on to the next action.

Cautions for using Resume

1. set retry limits
   • too many retries can waste time and resources, so set an appropriate number and interval.
2. determine if recovery is possible
   • make sure the error is temporary. a configuration issue on the server or an invalid request might not be resolved by retrying.
3. add logging
   • set up logging when errors occur so that you can analyze the cause if the problem recurs.

Resume summary

item	description
role	retries the module in case of an error and attempts to recover.
use cases	network errors, API response delays, temporary failover.
configuration elements	number of retries, retry interval, run only under certain conditions.
cautions	use it only for tasks that are likely to be resolved by retrying, and set conditions and limits to prevent it from repeating indefinitely.

When used effectively, the Resume feature can increase the reliability and automation of your workflows

OpenAI offers a variety of AI models, such as o1, GPT-4o, GPT-4o Mini, and GPT-4 Turbo. Each model differs in performance, speed, and cost, and you can choose the right model based on your project’s requirements.

Make.com is a powerful platform that makes it easy to implement automation using the OpenAI API. However, one thing to keep in mind when using the API is that different models have different token costs. In particular, the Chat GPT module on Make.com does notallow you to set input tokens, butyou can set output max tokens, so optimizing this can be an effective way to reduce costs.

Taking the GPT-4o and GPT-4o Mini models as an example, the input cost differs by a factor of 33 and the output cost differs by a factor of 25, and token consumption can vary depending on the structure of the Korean and English prompts. by understanding these differences, you can choose the best model for your project’s language and task characteristics.

in this article, we’ll compare the performance, suitability, and token cost of GPT o1, GPT-4o, GPT-4o Mini, and GPT-4 Turbo, and show you how to use them efficiently. Whether you are planning to use the OpenAI API for a long timeor are just getting started with automation, this information will help you understand the differences between the models and choose the best one for your project .

talknizer OPEN AI Token Calculator: “https://platform.openai.com/tokenizer”

GPT 01, GPT-4o, GPT-4o mini, GPT-4 turbo model feature comparison

model	performance	token cost (input/output, per million tokens)	speed	intended Use
o1	models with advanced inference capabilities, optimized for solving complex problems.	15.00 / $60.00	slow	tasks that require a high degree of accuracy and reasoning skills, such as science, coding, and math.
GPT-4o	versatile, high-performance model that can handle text, images, and audio.	5.00 / $15.00	moderate	general purpose model for a wide range of tasks.
GPT-4o mini	lightweight model that is fast, cost-effective and includes vision capabilities.	0.15 / $0.60	fast	projects where simple tasks, real-time processing, and cost-effectiveness are important.
GPT-4 turbo	2x faster than GPT-4o and half the cost.	10.00 / $30.00	very fast	generate large responses, repeat tasks, use APIs, and more.

1️⃣ GPT o1

• features: Provides the most precise inference capabilities, performs best on highly complex tasks
• good for: Writing scientific papers, designing complex algorithms, drafting legal documents.
• summary: Best for projects that require precision and accuracy.

GPT o1 is a model with GPT advanced reasoning capabilities, optimized for solving complex problems. as of January 25, 2025, it is the highest performing GPT model available today and is ideal for tasks that require a high degree of accuracy.

it is often used to handle challenging tasks such as analyzing complex data, writing research papers, and designing coding algorithms. it is useful for working on scientific papers, solving complex algorithmic problems, and drafting legal documents. API calls are relatively slow and can be expensive, so they’re used in projects where accuracy and quality are a priority.

The GPT o1 API costs $15.00 (input)/$60.00 (output) per million tokens and is slow. .

. 2️⃣ GPT-4o

• features: A versatile, high-performance model that provides balanced performance for a variety of tasks.
• good for: blog writing, translation, marketing content creation, medium-difficulty analytics tasks.
• summary: A general-purpose model that can be utilized for many tasks.

The GPT-4o model is a versatile, high-performance model that can handle text, images, and audio. it is suitable for a wide range of tasks and can be used for medium-difficulty tasks with good performance.

GPT-4o is typically used for a variety of tasks, including text generation, image description, translation, and marketing content creation such as blogs, YouTube transcripts, email drafting, and ad copy generation. The call rate when using the API is currently moderate and is used when you need to balance high-quality work with economic cost.

The GPT-4o API costs $5.00 (input)/$15.00 (output) per million tokens, with moderate speeds.

3️⃣ GPT-4o mini

• features: Lightweight model optimized for simple tasks, fast and low cost.
• ideal for: Real-time FAQ bots, social media captioning, and simple response processing.
• summary: An affordable choice for simple tasks and real-time processing.

The GPT 4o-mini model is a lightweight version of the 4o, optimized for simple tasks, offering fast response times and cost-effectiveness.

ideal for tasks that require fast response and low cost. for quick turnaround on simple tasks such as live chat responses, simple FAQ bots, and social media captioning. It is often used for large-scale projects or real-time services because it is very fast and cost-effective to make API calls.

GPT-4o mini costs $0.15 (input)/$0.60 (output) per 1 million tokens and is very fast.

4️⃣ GPT- turbo

• features: Optimized for high-volume tasks with fast processing speed and good performance.
• best for: Large data processing, repetitive tasks, real-time response systems.
• summary: Provides a balance of performance and cost-effectiveness for speed-critical jobs.

The GPT- turbo modelis twice as fast as the GPT-4o and half the cost, making it efficient for high-speed, high-volume jobs where real-time processing is critical.

ideal for jobs that require large amounts of data processing, real-time services, and fast response times. Used for repetitive tasks or large-scale user response systems (API-based) because it is the fastest and most cost-effective way to make API calls. for example, e-commerce customer support systems or large-scale data synchronization tasks,

GPT- turbo costs only $10.00 (input) / $30.00 (output) per million tokens, which is on the fast side,

Comparison ofGPT o1, GPT-4o, GPT-4o Mini, GPT-4 Turbo based on performance

1️⃣ Precision and Inference

• o1 > GPT-4o > GPT-4-Turbo > GPT-4o Mini
• description:
  the o1 offers the most precise inference power and excels at complex tasks. GPT-4o is a versatile, high-performance model that performs adequately on a wide range of tasks. The GPT-4-Turbo delivers compliant performance with fast processing speeds, while the GPT-4o Mini is optimized for simple tasks.

2️⃣ Cost-effectiveness

• GPT-4o Mini > GPT-4o > GPT-4-Turbo > o1
• description:
  The GPT-4o Mini is ideal for handling simple jobs at the lowest cost. The GPT-4o offers a medium balance of cost and performance. The GPT-4-Turbo has a slightly higher cost in proportion to its faster processing speed, and the o1 requires the highest cost with the highest performance.

3️⃣ Speed

• GPT-4o Mini ≥ GPT-4-Turbo > GPT-4o > o1
• explanation:
  GPT-4o Mini and GPT-4-Turbo are fast and suitable for real-time processing jobs. The GPT-4o offers standard speeds, while the o1 has relatively slow speeds with high precision.

model selection guide

choose the GPT-4o: 1️⃣ for complex problem solving and tasks requiring high accuracy

• choose the O1
  • examples of use: writing scientific papers, advanced data analysis, drafting legal documents.
  • why: When precision and reasoning skills are paramount.

2️⃣ A general-purpose model that can perform a variety of tasks

• GPT-4o is a good fit
  • example uses: creating blog content, describing images, translating, drafting emails.
  • why: Versatile and performs well on a variety of tasks.

3️⃣ Simple tasks where cost-effectiveness and fast response are important

• Consider the GPT-4o Mini
  • example uses: Running FAQ bots, generating social media captions, live chat.
  • why: Effectively handle simple tasks at low cost and fast turnaround.

4️⃣ For larger jobs and real-time processing

• Choose GPT-4o Turbo.
  • use cases: bulk data processing, real-time API responses, recurring jobs.
  • why: Fast and affordable, perfect for large-scale jobs.

---

Chat gpt (open ai )api token

In OpenAI’s token system, Korean and English arehandled differently. the number of tokens depends on the structure of the language and the length of the words, so even sentences of the same length use different numbers of tokens depending on the language. below, we’ll explain the differences in the token system between Korean and English. First, we’ll start with the concept of tokens, which is how OPEN AI’s API reads letters, and then we’ll discuss token costs and use cases, as well as tips for reducing costs when using the API.

1️⃣ What is a token?

• In OpenAI’s model, a tokenis the smallest unit of processing text data.
• one token consists of about one word or a few letters
  • example: “ChatGPT is great!” → 6 tokens.
  • example: “Hi, this is GPT.” → about 9 to 11 tokens.

2️⃣ Difference between tokens in Korean and English

1) English (English)

• english has spaces between words and a simple grammatical structure, so the number of tokens used in a sentence is relatively small.
• example
  • sentence: “Hello, how are you doing?”
  • tokens: 7
    • “Hello”, “,”, “how”, “are”, “you”, “doing”, “?”

2) Korean (Korean)

• korean tends to be a language with a lot of investigations (e.g., “은”, “은은”, “을”) and endings changes (e.g., “합니다”, “해요”), which makes words longer.
• when processing Korean, the model also chops up words and tokenizes them, consuming more tokens than an English translation of the same sentence.
• example
  • sentence: “Hello, it’s a beautiful day.”
  • tokens: 13-15
    • “Hi”, “do”, “,”, “today”, “weather”, “go”, “true”, “good”, “yes”, “yo”, “.”

3️⃣ Comparing the number of tokens in Korean and English

• in Korean, it is not uncommon for a sentence with the same content to consume 1.5 to 2 times as many tokens as in English, due to investigation, end inflection, word compounding, etc.
• example comparison
  • english: “I love learning AI.” → 5 tokens.
  • korean: “I like learning AI.” → about 12-14 tokens.

4️⃣ Differences in calculating token costs

1. The OpenAI API is priced based on the number of tokens, so a Korean task may cost more than an English task.
2. for example, for GPT-4-Turbo
   • input cost: $0.0015/1K tokens
   • output cost: $0.002/1K tokens
   • generating long sentences in Korean is likely to be more expensivethan in English.

5️⃣ Real-world use cases

• english: Efficient for generating short sentences, writing technical documentation, and optimizing API responses
  • example: “Write a summary of this report.” → about 6 tokens.
• korean: Used for customer service responses, translations, and user interface text generation
  • example: “Please write a summary of this report.” → about 12-15 tokens.

6️⃣ Optimization tips for using the Korean and English APIs

1. make concise requests: In Korean, longer requests consume more tokens, so write concise and clear requests
   • example: “Write a summary of the report” (O) → “Please write a detailed and thorough summary based on this report.” (X)
2. limit output length: Explicitly limit the number of output tokens in your request
   • example: “Please summarize in 50 characters or less.”
3. when working with translations: save tokens by making a request in English and receiving only the translated result in Korean.

conclusion

OpenAI offers a wide range of choices for users with a variety of AI models. the o1, GPT-4o, GPT-4o Mini, and GPT-4 Turbocan be utilized for specific projects based on their respective features and strengths.

the o1is best suited for jobs that require the most precise inference capabilities and high levels of complexity, and is ideal if you can tolerate its high cost and relatively slow speed. the GPT-4o, on the other hand, is a general-purpose model that offers balanced performance on a wide range of tasks, and the GPT-4o Miniis a low-cost model optimized for simple tasks and real-time response. The GPT-4 Turbooffers fast processing speeds and excellent efficiency for large-scale jobs.

model selection and maximum output token settingsare key to cost savings, especially when automating with Make.com and the OpenAI API. for example, GPT-4o and GPT-4o Mini have a 25x difference in output cost, so it is important to choose the right model based on the nature of the project and the difficulty of the task. for example, for SNS publication, we use GPT-4o Mini to reduce the number of text, and for blog publication, we use GPT-4o’s model to deliver accurate and in-depth information.

in addition, the difference in token processingbetween Korean and English is an important factor in the cost-effectiveness of our work. korean tends to consume about 1.5 to 2 times as many tokens as English, so we can optimize costs by making concise requests and limiting output length.

in make automation, the error handler break isresponsible for immediately abortingthe workflow when a fatal erroroccurs during the execution of a scenario. If an error occurs in a critical task, the break handler can be used to abort on death. you can add additional error handlers by right-clicking on the module to add an error handler.

you can see the role of breadk among the error handlers, usage situations, examples, and cautions on how to set it up.

Role of Break

1. stop execution immediately
   • immediately stops the execution of the scenario at the point where the error occurs.
   • any other tasks that were running will also be canceled, and no tasks will be executed after the module where the error occurred.
2. protecting data integrity
   • prevents processing or storing incorrect data when an error occurs.
   • protects sensitive data or processes from being corrupted.

When to useBreak

When you should use Break

1. when a fatal error occurs
   • when the error makes it unlikely that subsequent actions will perform correctly, or when you are concerned about data corruption.
2. when data integrity is important
   • when errors occur in operations where accuracy is critical, such as databases, financial transactions, user account updates, etc.
3. when it makes no sense to continue the process
   • when a required action (e.g., external API call, file creation, etc.) fails and the entire workflow must stop.

Examples of usingBreak

example 1: Financial transactions

• situation: An error occurs while processing a customer’s payment information.
• behavior
  • use Break tointerrupt the workflow because the payment data may be incomplete or stored incorrectly.
  • notifications can be sent to future customers to help them avoid the same error.

example 2: Database update

• situation: An error occurs during an operation to update customer information in your customer relationship management (CRM) system.
• action
  • immediately stop running the scenario to prevent incorrect data from being saved.
  • enable workers to manually correct data errors afterward.

example 3: Order fulfillment system

• situation: Your ecommerce site is processing customer order data and encounters an error in a specific module.
• action
  • stop the workflow to prevent order data from being corrupted or duplicated.
  • notify administrators of the error through the notification system.

How to set up Break

1. add an error handler
   • On the Edit scenario screen in Make.com, hover over the module where the error is likely to occur.
   • clickAdd error handler.
2. Select Break
   • from the error handler options, select Break.
3. save and test
   • after saving the scenario, test that the workflow breaks immediately when an error occurs.

Cautions when using Break

1. configure error handling: Before interrupting a workflow with Break, you should anticipate situations where errors might occur and configure an appropriate logging or notification system.
2. set up appropriate notifications: Set up notifications (email, Slack, etc.) to immediately notify your manager or relevant teams when an error occurs.
3. Recovering tasks stopped by Break: After a Break handler is executed, you need to design a process to manually or automatically recover stalled jobs.

Break is a powerful tool for ensuring data integrity and preventing further problems caused by fatal errors. when utilized in conjunction with other error handling options (Resume, Rollback, etc.), it can help you manage your workflows more effectively.

Break at a glance

item	description
role	immediately stopping execution when an error occurs, stopping further work and protecting data integrity.
when to use	in the event of a catastrophic error, when data integrity is critical, and when essential operations fail.
examples of use	payment information errors during financial transactions, preventing data corruption during database updates, preventing data duplication during order processing.
how to set it up	1. add an error handler → 2. Select Break → 3. Save and test.
cautions	you need to set up error prediction and logging, configure an appropriate notification system, and design a process for recovering aborted operations.

Break is a powerful tool that ensures data integrityand immediately stops a task in the event of a fatal error.It’s useful for critical processes like financial transactions, database updates, order processing, and more.Setting up Breakon Make.comprevents incorrect actions in the event of an error and enables reliable workflow management.

Ignoreis an error handling option in Make.com that allows you to ignore an error andcontinue running your workflow. This option is designed so that if a particular action fails, it doesn’t affect subsequent actions or the entire workflow.

What does Ignore do?

1. ignore and skip errors
   • if an error occurs, skip that action and run the next action.
2. continue running the entire workflow
   • if an error occurs in a non-essential task, the main task or process is not interrupted.
3. provide flexibility
   • if some failures in your workflow are acceptable, ignore them and process the remaining tasks.

When to useIgnore

When you should use Ignore:

1. non-essential actions may fail
   • when the failure of a specific action does not affect the overall flow of the workflow.
   • examples: logging, sending non-essential notifications, etc.
2. when only some of the multiple tasks are critical
   • when sending data to multiple platforms or services, and the rest of the task must continue to run even if an error occurs on a particular platform.
3. ensuring workflow reliability
   • when you need to ensure that your entire workflow doesn’t break in the event of an error.
4. when process continuity is important
   • situations where the workflow should continue even if some errors occur.
   • example: the main process completes even if an optional data update fails.
5. test phase
   • used in initial setup or test scenarios where errors are likely to occur.

Examples of usingIgnore

example 1:When uploadingsocial media postsfails

• situation: A workflow uploads a post to Facebook, Twitter, or Instagram.
• problem: The post fails due to a Facebook connection error.
• What Ignore does
  • skip uploading the Facebook post, but publish normally to Twitter and Instagram.

example 2: Failure tosave logs

• situation: Sending an email to a customer after saving the results of an API call as a log in your database.
• problem: Database connection error while saving logs.
• Ignore’s behavior
  • skip the log saving task, but execute the email sending task normally.

example 3: Data update fails, includingfile processing

• situation: When uploading multiple files to an FTP server, some file uploads fail.
• problem: Uploading certain files fails.
• What Ignore does
  • ignore the failed file and continue uploading the rest of the files.

To set up Ignore

1. add an error handler
   • on the Edit Scenario screen, hover over the module where an error is likely to occur.
   • clickAdd error handler.
2. Select Ignore
   • from the error handler options, select Ignore.
3. save and test
   • save the scenario, and verify that the workflow continues to run when an error occurs.

Cautions for using Ignore

1. don’t apply to critical jobs
   • we do not recommend using Ignore for critical jobs that require data integrity.
2. leave an error log
   • even if you ignore an error, save a log or send a notification to an administrator so that you can track the error.
3. check for dependent tasks
   • When using Ignore, make sure that the failure of that task doesn’t affect subsequent tasks.

Ignore at a glance

item	description
role	ignore the error and continue running the workflow.
use cases	when an error in a non-essential task should not affect the workflow as a whole.
examples	some social media uploads fail, logs fail to save, etc.
cautions	avoid using it on critical tasks, and save error logs so that you can track down the issue.

gNORE is a useful tool for maintaining continuity by ignoring errors andallowing workflows to continue running.It is effective when errors do not have a significant impact on the overall process, such as non-essential tasks or optional updates.It is not suitable for sensitive data or essential tasks, and should be used safely by tracking errors and recording the results.

Rollbackis an error handling option in Make.com that provides the ability to restore a previous state in the event of an error. it is designed to cancel any executed actions, if any, and return to the initial state before the error. it is primarily used in transaction-based operations where data integrity is important.

What does Rollback do?

1. restore the state before the error
   • undo the result of an operation to the state it was in before the error occurred.
2. cancel an already executed operation
   • when an error occurs, actions that have already been processed are also rolled back.
3. ensure data integrity
   • maintain consistency between databases, financial transactions, or related operations.

when to use it

When you need to use rollback:

1. transaction-based operations
   • when multiple actions are chained together to form a transaction, and if some actions fail, the entire transaction needs to be canceled.
   • examples: bank transfers, purchasing processes, order fulfillment.
2. when data integrity is critical
   • when a single error has the potential to skew data or cause it to be stored incorrectly.
3. when task completion is dependent
   • when part of a task fails, the rest of the task must be invalidated.
   • example: failure during customer account creation, deleting data that has already been created.

examples

example 1: Bank transfer

• situation: Withdrawing money from customer A’s account and depositing it into customer B’s account.
• problem: An error occurs during the deposit to customer B’s account.
• Rollback’s behavior
  • restore the amount withdrawn from Customer A’s account.
  • cancel the entire remittance process to ensure data consistency.

example 2: Fulfillment system

• situation: You’re processing a customer’s order on your eCommerce platform, taking payment, updating inventory, and saving the order record.
• problem: An error occurs while saving the order history.
• Rollback’s behavior
  • cancel payments and inventory updates that have already been processed, restoring them to their original state.

example 3: Data synchronization

• situation: Synchronizing your CRM system with an external database.
• problem: A network error occurs in the middle of the data synchronization.
• Rollback’s behavior
  • revert to the original state by canceling the already synchronized data.

To set up Rollback

1. add an error handler
   • On the Edit Scenario screen in Make.com, hover over the module where the error is likely to occur, and click Add error handler.
2. Select Rollback
   • from the error handler options, select Rollback.
3. save and test
   • save the scenario, and test that your work is restored when an error occurs.

Cautions for using Rollback

1. verify that the action is recoverable
   • not all actions might be rollbackable. for example, sending emails or updating external systems is difficult to restore.
2. transactional design
   • To use Rollback, you need to ensure that your workflow has a transactional design.
3. data loss prevention
   • Be careful, as Rollback can cause unintentional data loss if set up incorrectly.
4. keep a record of your actions
   • Keep a log or history after a rollback so that you can analyze the issue.

Rollback summary

item	description
role	restore a previous state in case of an error (Undo).
use cases	bank transfers, transaction-based data processing, order fulfillment, and more.
precautions	ensure that all operations are restoreable, and avoid unintentional data loss.
examples	restoring customer transfers when they fail, canceling payments and inventory updates when fulfillment fails.

Rollback is an essential feature to ensure data integrity and is a robust option designed to help you maintain stability in the event of an error in a critical transactional process]