Elasticsearch errors in API response

Deleting a task may return an error if the task was not (yet) indexed by the search engine, even if the task was successfully deleted.

Api_task.php:233

    try {
      $this->elasticsearch->delete('task', $task_id);
      $this->elasticsearch->index('user', $this->user_id);
    } catch (Exception $e) {
      $additionalMsg = get_class() . '.' . __FUNCTION__ . ':' . $e->getMessage();
      $this->returnError(105, $this->version, $this->openmlGeneralErrorCode, $additionalMsg);
      return;
    }

Is it intended behavior to return that 105 error?

Start at Api_task.php:233 and reproduce deleting a task before it is indexed by Elasticsearch. Trace how the caught exception becomes API error 105, then confirm the intended response behavior with the project maintainers. Done means the API no longer reports a misleading result, or the intended error behavior is explicitly confirmed and covered.