What is the difference between Async and After BR?

[a41022639]

Hello Community,

I am bit confused, what is the difference between the async and after BR and when should we use it.

[Dr Atul G- LNG · Accepted solution]

Hi @a41022639 

async
-When the scheduler runs the scheduled job created from the business rule.
The system creates a scheduled job from the business rule

after
-After the user submits the form and after any action is taken on the record in the database.

https://www.servicenow.com/community/now-platform-forum/difference-between-asyn-and-after-business-r....

[Akshay03 · Accepted solution]

Hello,

The "Async" (asynchronous) and "after" (synchronous) are terms used to describe the execution timing of business rules. Understanding when to use each depends on the specific requirements of your business logic.

Async execution : Asynchronous business rules are executed after the database operation completes and the response is returned to the user.

After execution : Synchronous business rules are executed immediately after the database operation is performed but before the response is sent to the user.

[Abhishek_Thakur · Accepted solution]

Hello @a41022639 

After business rule executes, after the record inserted into the database, whereas async business rule works in the background asynchronously as it names convey.

If you don't want your user interaction to be on hold, you should go with async business rule it usually prefers for web services. Because sometime while using the after-business rule, user experience may be on hold.

[Dr Atul G- LNG · Accepted solution]

Hi @a41022639 

async
-When the scheduler runs the scheduled job created from the business rule.
The system creates a scheduled job from the business rule

after
-After the user submits the form and after any action is taken on the record in the database.

https://www.servicenow.com/community/now-platform-forum/difference-between-asyn-and-after-business-r....

[Akshay03 · Accepted solution]

Hello,

The "Async" (asynchronous) and "after" (synchronous) are terms used to describe the execution timing of business rules. Understanding when to use each depends on the specific requirements of your business logic.

Async execution : Asynchronous business rules are executed after the database operation completes and the response is returned to the user.

After execution : Synchronous business rules are executed immediately after the database operation is performed but before the response is sent to the user.

[Abhishek_Thakur · Accepted solution]

Hello @a41022639 

After business rule executes, after the record inserted into the database, whereas async business rule works in the background asynchronously as it names convey.

If you don't want your user interaction to be on hold, you should go with async business rule it usually prefers for web services. Because sometime while using the after-business rule, user experience may be on hold.

[IThelen]

It also depends on what is updated.
Usually you use after and async to update related records. If you update records that the user will see on the from, e.g. in a reference field, you will prefer the after method. Updates that will take realy long, e.g. closing all child incidents of a major incident, will usually run async, to not block the user session.
From the technical best practices
https://developer.servicenow.com/dev.do#!/guides/washingtondc/now-platform/tpb-guide/business_rules_...:

after	Use to update information on related objects that need to be displayed immediately, such as GlideRecord queries.
async	Use to update information on related objects that do not need to be displayed immediately, such as calculating metrics and SLAs.