In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Bug report

A lot of times if schema history topic is large, then the task takes a lot of time to start since it includes schema history recovery in it. This leads to task status being wrongly returned by connect runtime for that duration. Reason is runtime returns the last updated status in the status topic. So if the task was restarted after a failure, the status returned by runtime until the task's `start` method completes would be FAILED.

To solve this, task's `start` method should ideally be lightweight. Hence we want to move the history recovery part out of the task's `start` method.