Hi @owl1234-ltl,
Thank you for clarifying your question. We apologize for not testing this specific case in version 0.5.9.4; we conducted our tests in our development branch. The bug regarding “50058” does exist in version 0.5.9.4 but has already been fixed in our latest version. However, we still cannot reproduce the issue with “50056”.
Thank you for your understanding, and please let us know if you have any further questions or details to share!