Your title doesn't match the site's standard.
Is this an appropriate use of async/await combined with Task continuation?
The title is what you want out of the review however pretty much all Code Review questions would be titled the same as yours and is generally not great. As such you should change the title to what your code does.
There is additional information in the in the help center that BCdotWEB linked to.
Titling your question
State what your code does in your title, not your main concerns about it. Be descriptive and interesting, and you'll attract more views to your question.
Here are some examples of titles that are unacceptable because they are too generic:
- How can I make this faster? (Everyone prefers faster code. The (performance) tag can convey this desire.)
- Simplify this chain of if statements (Applies to too many questions.)
- Ruby function needs refactoring (Reviewers will decide if it needs refactoring. You don't have to ask for it in the title.)
- Is this good OOP design? (Title is not distinctive.)
- Online judge says Time Limit Exceeded (Title tells us nothing beyond what would be conveyed by (programming-challenge) and (time-limit-exceeded) tags.)
Furthermore, you should omit these kinds of superfluous phrases from titles, because these requests are implicit in every Code Review question:
- Can you critique my …
- Please help me…
- … needs improvement
- Reduce the complexity of…
The norm is to summarize the goal of the code in the title. Some typical titles are:
- Project Euler 9: finding a Pythagorean triplet
- Game of Life with a Swing UI
- View controller for smoking cessation iOS app
- Validating inputs for a vacation request form
If your code does not have a goal, then it is likely that your question contains hypothetical code, or that you are asking about best practices in general rather than for a review of your code. Such questions are off-topic for Code Review.