Recompiling it made the problem go away temporarily. It hasn't fixed it. Fixing will require changing the code or using plan guides or query store forced plans (if an upgrade to SQL 2016 is an option) to ensure there's only one possible plan choice for the procedure.