There are instances of errors in Sentry that a duplicate slug was set, or tried to be set for a session. It appears when this happens that no record is written and may be causing an error to the end user. (The id being looked up was event id 🤦♂️)
https://sentry.io/organizations/that-conference/issues/1718298523/?project=1796530&query=is%3Aunresolved
The logic built into the session slug is that if a duplicate is found that it's ID will be used in place of a title-based slug. In theory this error should not happen 😄 .
The task here is to discover if this is affecting the end user's experience investigate the path which is allowing this to happen. In the session in the above link, the referenced session id was not in the database which says it probably affected the user.
dataSources/cloudFirestore/session.js > genUniqueSlug()
What I am seeing here is that if there is a duplicate slug for the suggested slug for a new session this error is being thrown. This at an error level is not correctly, it is more informational or maybe (but probably not) a warning. The reason being is that with the condition the id is written into the slug value.
There are instances of errors in Sentry that a duplicate slug was set, or tried to be set for a session.
It appears when this happens that no record is written and may be causing an error to the end user.(The id being looked up was event id 🤦♂️)https://sentry.io/organizations/that-conference/issues/1718298523/?project=1796530&query=is%3Aunresolved
The logic built into the session slug is that if a duplicate is found that it's ID will be used in place of a title-based slug. In theory this error should not happen 😄 .
The task here is to discover if this is affecting the end user's experience investigate the path which is allowing this to happen. In the session in the above link, the referenced session id was not in the database which says it probably affected the user.
dataSources/cloudFirestore/session.js > genUniqueSlug()
What I am seeing here is that if there is a duplicate slug for the suggested slug for a new session this error is being thrown. This at an
errorlevel is not correctly, it is more informational or maybe (but probably not) a warning. The reason being is that with the condition the id is written into the slug value.