Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
When I Do Task.Init() And Then A Execute_Remotely(), The Task Is Being Aborted Rather Than Be In Draft. Am I Missing Something?

When I do Task.init() and then a execute_remotely(), the task is being Aborted rather than be in Draft. Am I missing something?

  
  
Posted 2 years ago
Votes Newest

Answers 4


TrickySheep9 you can also add the queue to execute this task:

task.execute_remotely(queue_name="default")So it will enqueue it too 🙂

  
  
Posted 2 years ago

I don’t want to though. Will run it as part of a pipeline

  
  
Posted 2 years ago

AgitatedDove14 - thoughts on this? I remember that it was Draft before, but maybe because it was in a notebook vs now I am running a script?

  
  
Posted 2 years ago

the task is being Aborted rather than be in Draft. Am I missing something?

Yes, the reason is for not missing anything that you might have reported on it.
And usually execute_remotely will get the execution queue as a paramter (i.e. immdiatly launching the Task)
You can now (starting v1.0) enqueue an aborted Task so it should not make a difference, you can also reset the Task and edit it in the UI

  
  
Posted 2 years ago
583 Views
4 Answers
2 years ago
one year ago
Tags