You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was recently creating a release in the 'Build' tab of the Studio, and the indexing step failed when my ElasticSearch became disconnected. When I tried creating a new indexing job from the GUI, I saw the message:
ERR {0.18s} index(indexer_env='local',target_name='mygeneset_20210127_jox8gtpg',index_name='mygeneset_current'): finished ["Index already 'mygeneset_current' exists, (use mode='purge' to auto-delete it or mode='resume' to add more documents)"]
I was able to resume the job from the commandline using the suggested mode=resume, but I think it would be more user friendly if there was a button somewhere on the GUI for resuming a failed indexing job.
The text was updated successfully, but these errors were encountered:
I was recently creating a release in the 'Build' tab of the Studio, and the indexing step failed when my ElasticSearch became disconnected. When I tried creating a new indexing job from the GUI, I saw the message:
I was able to resume the job from the commandline using the suggested
mode=resume
, but I think it would be more user friendly if there was a button somewhere on the GUI for resuming a failed indexing job.The text was updated successfully, but these errors were encountered: