You could also use Wait 0 seconds, should have the same result.
If you're interested in the reason why this action might be needed in some cases:
When an object is created, it sometimes needs a frame to "prepare itself".
During that time, you can set e.g. parameters or coordinates, but the object isn't interactive yet, thus can't be affected by other plugins/behaviors.
To give an example, the Text object expression Text.TextHeight doesn't return the correct height in the same frame as setting the text.
This means, when you change the text and put an action underneath that, calling the .TextHeight expression, it will not return the correct number.
But if you put a Wait dt seconds in between, it will work.
So, if you have an issue like this again, where an object just doesn't seem to react or an object expression doesn't return what it should, you might wanna wait a frame.