@mherrb your feedback made it, its a problem with talks that had schedule changes that the redirect url throws this error, we ran a fix