---
title: "Discussion on \"Apex Queueable Chaining: State Across Async Invocations\" | Hashnode"
description: "Discussion on \"Apex Queueable Chaining: State Across Async Invocations\". A multi-step async workflow involves processing 100K records across five distinct stages. Each stage is too much for one transaction. Queueable chaining keeps the work going across invocations without losing state, governor limits, or the a"
url: "https://hashnode.com/posts/apex-queueable-chaining-state-across-async-invocations/6a53c51941361a4465e6b87a"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Apex Queueable Chaining: State Across Async Invocations](https://sapotacorpvn.hashnode.dev/apex-queueable-chaining-state-across-async-invocations?utm_source=hashnode&utm_medium=feed)

A multi-step async workflow involves processing 100K records across five distinct stages. Each stage is too much for one transaction. Queueable chaining keeps the work going across invocations without losing state, governor limits, or the a

Jul 12 · 7 min read · sapotacorpvn.hashnode.dev  
Read the article

-   [#salesforce](https://hashnode.com/tag/salesforce)
-   [#apex](https://hashnode.com/tag/apex)
-   [#queueable](https://hashnode.com/tag/queueable)
-   [#async](https://hashnode.com/tag/async)
-   [#apex-development](https://hashnode.com/tag/apex-development)

## Written by

[SapotaCorp](https://hashnode.com/@sapotacorpvn)

@sapotacorpvn · Hanoi, Vietnam

  
[View profile](https://hashnode.com/@sapotacorpvn)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.