Lakshmi Narayanan R

@ramfattah thank you. Is there a way to resolve this? What is the reason for this error? I am currently trying to create the orchestrator, to migrate from Dispatch.

@ramfattah could you please let me know any update? I am waiting on moving my dispatch to orchestrator as I need to recognize multiple intents.

@munozemilio @ramfattah Hey, thank you for the participation so far in resolving this. Any updates? Cuz as mentioned earlier , I am looking to move dspatch to orchestrator in Luis,...

@ramfattah @ceciliaavila Hey guys, can you please let me know if there's an update? Would be great if we can fix/bypass this, as we need the Orchestrator. Thanks!

@sw-joelmut Thank you for the quick response! Just to get my understanding clear, don't we need the pretrained model to use Orchestratr efficiently? Does not providing the `--in` give a...

@sw-joelmut Okay, I understand. The json file causing error is the one that has the pretrained model. Thus, skipping it would mean that I cannot use the pretrained model for...

@sw-joelmut I do not think it is possible to byPass, since the error is from the ORchestrator model, that is created by `bf orchestrator:basemodel:get --out model`. Could you please confirm...

@sw-joelmut Thank you for clarifying. I was able to bypass and not have the error, by changing the '--in' argument to point to the data sources. The Orchestrator Snapshot was...

@sw-joelmut To be more clear, I was able to create the **Orchestrator Snapshot** as shown below  Now, I am trying to import this into Luis, as an instance, to...

@ramfattah @tracyboehrer @ceciliaavila @sw-joelmut , Dear team, after having few back and forth with @sw-joelmut , I understood that the error was giving the param value for `--in` argument as...