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

Provide clear error message instead of Null Pointer Exception(NPE) #241

Open
longquanzheng opened this issue Sep 19, 2024 · 0 comments
Open

Comments

@longquanzheng
Copy link
Contributor

longquanzheng commented Sep 19, 2024

When workflow type, workflowState, RPC are not registered, what are the errors we are thrown today?

Some of them are NPE which is hard to troubleshoot. We should provide clear message that these entities are not registerd, maybe even provide potential reasons (delete or rename), and how to fix them.

Also similarly:

  • data attribute
  • search attribute
  • Signal channel
  • InternalChannel
    What are the behavior when they are used without proper registered?
@longquanzheng longquanzheng changed the title Provide clear error message when state is not present Provide clear error message when state or workflow is not registered Nov 27, 2024
@longquanzheng longquanzheng changed the title Provide clear error message when state or workflow is not registered Provide clear error message instead of Null Pointer Exception(NPE) Dec 17, 2024
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

1 participant