amulyavarote

@paulyuk and @greenie-msft Should we close this if we already create an issue in the other document?

Closing this based on the discussion in #735. This issue will be reopened if needed.

> > Ok, took me a while to get the right context here (side note, really need to link a condensed design / exec summary). > > For Python I...

> At a high level, I'm in favor of this proposal. I do have a few questions, though. > > For the workflow management APIs, you mention in the Cons...

> This proto is a part of unreleased Dapr, right? We should wait for the next release before changing this here. Thoughts? > > /cc @XavierGeerinck Yes. Makes sense. We...

Looks good to me!

Example of exception details: Dapr.Actors.ActorMethodInvocationException: Remote Actor Method Exception, DETAILS: Exception: NotImplementedException, Method Name: ExceptionExample, Line Number: 14, Exception uuid: d291a006-84d5-42c4-b39e-d6300e9ac38b

Current logs are quite generic. They should say something like "Actor method invoke exception". We have to add details to this message.

Example of exception details: Dapr.Actors.ActorMethodInvocationException: Remote Actor Method Exception, DETAILS: Exception: NotImplementedException, Method Name: ExceptionExample, Line Number: 14, Exception uuid: d291a006-84d5-42c4-b39e-d6300e9ac38b

@paulyuk I also think the priority should be given to configuration API. We can take out Observability from the list as an example is already included in the tutorials section.