Minecraft – My command blocks are forgetting coordinates!

I built a set of command blocks on a single-player creative world to work out the kinks, and it worked correctly. It first uses /execute to find an instance of an item with a specific name and teleports the nearest player to a specific set of coordinates, then moves down the chain, using /execute to make the item dropped kill itself, play a sound on the destination spot and play a particle effect on the destination spot. Again, this all worked on a solo creative world.

When I took it to my realms world, I was able to build the command blocks the same way, but the blocks completely forget the coordinates for the destination, replacing them with ### ## ### any time the condition for the first block is met or the editor for the block is re-entered. The only differences are:

• The blocks in the Realm world are hidden underground instead of on the surface, close to some redstone torches (even though the blocks were marked not to be redstone-dependent)

• The name of the item was changed for the Realm version. I tried the original name of the item, and it did not fix the issue.

• I added a ticking area around the blocks so it would function anywhere, and thought that might be the problem, but I removed the ticking area, and it did not enable the blocks to remember the coordinates.

• In reply to ExpertCoder14's comment: The coordinates in question are 170 67 -22. Not sure why that has anything to do with the profanity filter, but that is somewhat hysterical given the place I am directing the teleport to.

I have another command block in the realm (a small distance away at the spawn point) that is triggered by redstone dust and copies a box of stuff when the correct page in a book is read, and it still functions (without a ticking area because there needs to be a player there to read it).

Here's the initial command:
/execute @e [type=item, name="example name"] ~ ~ ~ tp @p x y z

A comment mentioned that it may be a profanity filter issue. The exact coordinates are 170 67 -22, and I am playing on a Switch. Not sure how that violated the filter, but I can try to find a different location for the destination.