You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to be able to trace errors thrown on the frontend, it's useful to have a request id header in the response that will be rendered in error toasts that the user sees. We can then query the backend logs based on the ids and trace the error more effectively.
@itegulov This looks good to me. We will display the 'traceparent' header from the response in the toast and the whole request + error can be successfully traced from a screenshot or similar.
In order to be able to trace errors thrown on the frontend, it's useful to have a request id header in the response that will be rendered in error toasts that the user sees. We can then query the backend logs based on the ids and trace the error more effectively.
caused by near/fast-auth-signer#15
The text was updated successfully, but these errors were encountered: