-
Notifications
You must be signed in to change notification settings - Fork 4
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
When invoke flow, I got request failed to be processed. #6
Comments
I got the same error, and I have no idea. Could you please help us? @s8sg |
It seems the name of flow function |
@s8sg Sorry, I have found the problem. Link to https://github.com/faasflow/runtime/issues/1 |
@sherry10 Did you found the solution ? |
@sherry10 Can you share how to fixing this problem? |
@s8sg @tim64195419 I have changed several workflow names and have found that the url |
@sherry10 I follow your step then solved function name is 10 problem, but another problem is when set directfunction=true, faasflow pipeline can't pass the value with s3(minio) . Have you got this problem? |
@tim64195419 Did you solve the latter problem with directFunctions=true? It also happens to me when i try to invoke both replica pods of a function but with directFunctions=true, just one is invoked always as if load balancing not works from the gateway.. |
Hack solution here: faasflow/runtime#1 (comment) |
I don't know how to fixing this problem?
I got deploy/function logs look like
The text was updated successfully, but these errors were encountered: