Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run Playbooks - Returning Error in CLI, but Playbook Run is Success in UI #145

Open
jacognigy opened this issue Nov 2, 2023 · 2 comments

Comments

@jacognigy
Copy link

I'm using the command for "run playboosk": https://github.com/Cognigy/Cognigy-CLI#command-run

When I run the command with a test config file (with just 1 playbook) I get the following error:

jna@x-x:~$ cognigy run playbooks playbook_test.json
/home/jna/.nvm/versions/node/v18.15.0/lib/node_modules/@cognigy/cognigy-cli/build/utils/RestAdapter.js:76
        throw new BadRequestError_1.BadRequestError(data.title || data.error, data.detail || data.error_description, data.status, data.details);
              ^

Not Found: Playbook run does not exist
    at RestAdapter.handleError (/home/jna/.nvm/versions/node/v18.15.0/lib/node_modules/@cognigy/cognigy-cli/build/utils/RestAdapter.js:76:15)
    at RestAdapter.request (/home/jna/.nvm/versions/node/v18.15.0/lib/node_modules/@cognigy/cognigy-cli/build/utils/RestAdapter.js:42:22)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /home/jna/.nvm/versions/node/v18.15.0/lib/node_modules/@cognigy/cognigy-cli/node_modules/@cognigy/rest-api-client/build/GenericAPIFn.js:12:26
    at async Timeout._onTimeout (/home/jna/.nvm/versions/node/v18.15.0/lib/node_modules/@cognigy/cognigy-cli/build/lib/playbooks.js:71:37) {
  msg: 'Playbook run does not exist',
  httpStatusCode: 404,
  httpStatusText: 'Not Found',
  details: {}
}

Node.js v18.15.0

However, when I log into the UI of the Platform I can see the run from the Playbook with status succeeded.

I've tried adjusting the config.json file to update the timeout, but it doesn't wait as long as identified before the error is returned (ex. I set it to 30 or 60, and it's just as short as 10).

@XavierJordaMurria
Copy link
Collaborator

Hi,
thanks for reporting this.
I will create a ticket to investigate this.
I will let you know once we schedule it in.

@Heikum
Copy link

Heikum commented Dec 10, 2024

@XavierJordaMurria this is still the case

Any updates?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants