Hi @Charles Herron
Have you tried to reproduce the issue directly on Planner (not Teams Planner)?
Based on our research, this issue appears to be a known issue caused by a recent standard service deployment that contained a bug in the code.
This issue has been successfully fixed, please try again.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.