As part of https://jira.camunda.com/browse/OPT-2428, we started storing whether or not activity instances and user tasks have been cancelled. However, we only know that information about user tasks from the activity imports, so it added a new user task upsert type. To avoid the completed activities including these upserts in its bulk batches, we should instead change the engine API to return this information when Optimize imports User Tasks themselves.

Note this will involve an engine and Optimize change

ATs:

• User Task cancellation state is stored on import of user tasks
• We don't create user tasks when importing activity instances