- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-20-2019 04:05 AM
hi,
I have question ,why Previous object is not accessible in async business rule?
I had searched this on community but I didn't get it.plz tell me why previous object is not accessible...
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-20-2019 04:09 AM
Hi Ashwini,
previous object is not accessible in an async business rule because async business rule doesn't run immediately when record is inserted/updated instead it runs at specific time in backend after the transaction of insert/update happens i.e. asynchronously; hence system won't know what was the previous value for any field hence previous object won't make sense in that business rule
Mark Correct if this solves your issue and also mark Helpful if you find my response worthy based on the impact.
Thanks
Ankur
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-24-2023 10:02 PM
I made a 2 part video providing details, examples and possible pitfalls and fixes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-07-2025 04:49 AM
The "previous" object is not accessible in an asynchronous (async) Business Rule because an async rule runs after the original database transaction is complete. Since the transaction is over by the time the async rule executes, the system doesn't have access to the record's state before the changes were made, making the "previous" object unavailable.
