Dustin N.

hi Chandrahaas J. yes, that is a solid plan. If you set the session id and and project name in a middleware layer, the workflow execution code you can explicitly set the session on any spans you create

hi Andrei L. can you tell us a little more about your postgres setup? Are you using a custom schema?

hi WC this is the support channel for Phoenix, please check in Arize AX Support !

I can make an issue for you to discuss whether or not we should expose setting notes via the API/client

ah yeah, I think we blocked that from the client

hi Darshan T. can you try creating the annotation with the name "note"? We treat those as special (I think you used "notes" here)

hi Tarun K. please create an tracking issue so we can discuss with the team, we understand that errors can sometimes be difficult to read

in which case you can definitely get a conflict

if it's truly a new database I am confused as to why that would trigger a new mutation, but are you running two applications with separate tables all in the same database?

hmmm this is using postgres?