Yes, I started seeing the same thing. As a workaround, I am running a script (via Keyboard Maestro) to create the block of events I was previously creating via the shortcut. The script is
tell application "Fantastical"
parse sentence "Exercise tomorrow at 8am /timeblock" with add immediately
parse sentence "Morning routine tomorrow at 9am /timeblock" with add immediately
parse sentence "Email tomorrow at 10:15-10:30am /timeblock" with add immediately
parse sentence "BigRock tomorrow at 10:45am-12:15pm /timeblock" with add immediately
parse sentence "BigRock tomorrow at 12:45pm-2pm /timeblock" with add immediately
parse sentence "LittleRocks tomorrow at 2:15pm-4pm /timeblock" with add immediately
parse sentence "Rss/news tomorrow at 4:15pm-5pm /timeblock" with add immediately
parse sentence "Shutdown tomorrow at 5-5:45pm /timeblock" with add immediately
parse sentence "Reading tomorrow at 7-8:15pm /timeblock" with add immediately
end tell
On my computer it does what my multiple-action shortcut did - it creates the first event and then gives the error message. But the second and following events never get created.
So because yours only creates one event, it “works” to that extent, but the “unable to communicate…” error still happens.