/api/workflow/{workflowId} endpoint not working in swagger

[sudouser777]

Describe the bug
Get the workflow by id(/api/workflow/{workflowId}) endpoint is not working

To Reproduce
Steps to reproduce the behavior:

1. Go to 'http://<conductor_ip>:8080/swagger-ui/index.html?configUrl=/api-docs/swagger-config'
2. Click on '/api/workflow/{workflowId}' endpoint. It's not working. When I click on it page is stuck (not responding)

Expected behavior
It should give the response with workflow details of given workflow id.

Screenshots

Additional context
Add any other context about the problem here.

[apanicker-nflx]

@komatiraju032 What type of persistence layer are you using? Do you see any errors in the server logs?

[sudouser777]

@apanicker-nflx I am using default configuration(docker-compose.yml). And For your information endpoint is working from postman.

[maheshyaddanapudi]

No errors observed but the issue happens only in Swagger UI. I have opened a discussion thread #2192

[sudouser777]

@apanicker-nflx @maheshyaddanapudi it's not working because of this issue OAI/OpenAPI-Specification#822

[maheshyaddanapudi]

@komatiraju032 is there any specification for a work around it different way to configure ? I couldn't directly find any in their Read Me. I'll explore too.

[sudouser777]

@maheshyaddanapudi I found one more related issue on stackoverflow Swagger UI freezes after API fetch and browser crashes

[aravindanr]

@komatiraju032 we believe its because of the com.google.protobuf.Any type that the inputMessage and outputMessage fields in Task class. Excluding those fields in Swagger definition should solve the issue. We will get to it asap.

[sudouser777]

@aravindanr I have fixed the issue with the information you have provided. I also created a PR #2210

[aravindanr]

Thanks @komatiraju032 . I left a minor comment in the PR.