Skip to content
This repository was archived by the owner on Dec 13, 2023. It is now read-only.

UI Workflow Executions Grid not loading #2942

Closed
jegadjame opened this issue Apr 22, 2022 · 15 comments
Closed

UI Workflow Executions Grid not loading #2942

jegadjame opened this issue Apr 22, 2022 · 15 comments
Labels

Comments

@jegadjame
Copy link

Hi ,
I am using node-v16.14.2-x64 , jdk11, conductor-server-3.3.4-boot and downloaded latest code. When i trigger workflow, I am not seeing any data in Workflow Executions Grid. But records are getting processed. I can see data in Task Queue.

Please let me know if anything i am missing.

image

Thanks,
Jegadeesh

@jegadjame jegadjame added the type: bug bugs/ bug fixes label Apr 22, 2022
@jxu-nflx
Copy link
Contributor

Hello @jegadjame when that page load, it will try to call this api /workflow/search?start=0&size=15&sort=startTime:DESC&freeText=*&query=. Can you try run that API directly to see whether you are getting any response back? Also, the workflow execution search requires ES for indexing, do you have that enabled?

@manishkushwaha1412
Copy link

I am also facing this issue, tried calling API it seems API itself is not returning response. I tried it through swagger by same input provided in the browser network tab.
Through UI - http://localhost:5000/api/workflow/search?start=0&size=15&sort=startTime%3ADESC&freeText=%2A&query=
Through Swagger - http://localhost:8080/api/workflow/search?start=0&size=100
swagger search i did open without any condition to get at least some result. However, I didn't get the same.

Do you have any update on this? Appreciate your response.

@manishkushwaha1412
Copy link

Also, when I trigger workflow though URI its actually showing workflow but still execution is not as expected. I am following below official documents
https://netflix.github.io/conductor/labs/beginner/
Task created thought Post man as explain, workflow created through postman, executed workflow though postman (not working). However, workflow executed though UI http://localhost:5000/workbench is showing workflow but not as expected as explained in https://netflix.github.io/conductor/labs/beginner/

image

@jegadjame
Copy link
Author

jegadjame commented Apr 27, 2022

I am also facing this issue, tried calling API it seems API itself is not returning response. I tried it through swagger by same input provided in the browser network tab. Through UI - http://localhost:5000/api/workflow/search?start=0&size=15&sort=startTime%3ADESC&freeText=%2A&query= Through Swagger - http://localhost:8080/api/workflow/search?start=0&size=100 swagger search i did open without any condition to get at least some result. However, I didn't get the same.

Do you have any update on this? Appreciate your response.

I am not getting any response through swagger 'http://localhost:8080/api/workflow/search?size=100&freeText=%2A'
{
"totalHits": 0,
"results": []
}

@aravindanr
Copy link
Collaborator

Related to #2959

@jxu-nflx
Copy link
Contributor

jxu-nflx commented May 2, 2022

@jegadjame Can you check your config to make sure the es index is enabled: https://github.com/Netflix/conductor/blob/main/server/src/main/resources/application.properties#L19 Also if you are running it locally, please make sure you have the ES docker container up running as well

@manishkushwaha1412
Copy link

@jxu-nflx in below file, do you want to change false to true and give it a try ? when i did that I started getting some another exception. Server is getting started but UI is not able to call service exposed to 8080 port.
https://github.com/Netflix/conductor/blob/main/server/src/main/resources/application.properties#L19

@jxu-nflx
Copy link
Contributor

@manishkushwaha1412 if you don't have that config set to true, then basically means your UI search function will be broken, i.e. you couldn't search any workflow executions in UI.

Server is getting started but UI is not able to call service exposed to 8080 port.
What is the error you are seeing? Are you able to call any server api at all?

@edoang
Copy link

edoang commented May 23, 2022

Hi @jxu-nflx , today i've cloned the latest release.
docker-compose build and docker-compose up.
i have the same behaviour, elastic is up on localhost 9200.

docker/server/config/config.properties :

conductor.indexing.enabled=true
conductor.elasticsearch.url=http://es:9200

can you help me find the problem?

@jxu-nflx
Copy link
Contributor

jxu-nflx commented May 25, 2022

Hi @jxu-nflx , today i've cloned the latest release. docker-compose build and docker-compose up. i have the same behaviour, elastic is up on localhost 9200.

docker/server/config/config.properties :

conductor.indexing.enabled=true conductor.elasticsearch.url=http://es:9200

can you help me find the problem?

you need to make the changes in the config-local.properties file: https://github.com/Netflix/conductor/blob/main/docker/docker-compose.yaml#L6

Then docker-compose build and docker-compose up.

To verify that the change did happen, you could ssh into the conductor server container and check the property file under /app/config/: https://github.com/Netflix/conductor/blob/main/docker/server/Dockerfile#L31

@edoang
Copy link

edoang commented May 26, 2022

@jxu-nflx oh so simple :) thank you very much!

@manishkushwaha1412
Copy link

@jxu-nflx
I am not able to build it locally even through docker-compose as well. Its giving.

@jxu-nflx
Copy link
Contributor

jxu-nflx commented May 31, 2022

@jxu-nflx I am not able to build it locally even through docker-compose as well. Its giving.

what is the docker-compose command you use? And what is the error message? If its about Mac M1, please refer to this thread: #2975

@jxu-nflx jxu-nflx removed the type: bug bugs/ bug fixes label May 31, 2022
@github-actions
Copy link
Contributor

This issue is stale, because it has been open for 45 days with no activity. Remove the stale label or comment, or this will be closed in 7 days.

@github-actions github-actions bot added the Stale label Jul 16, 2022
@github-actions
Copy link
Contributor

This issue was closed, because it has been stalled for 7 days with no activity.

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

No branches or pull requests

5 participants