This question was solved by David Turner.
The error message in your history indicated that it was Twilio that reported the error. So the message was sent successfully from the Workflow, but then Twilio rejected it. In looking at SV's Twilio logs, it appears the message was flagged as going against the carrier guidelines. Here's link to the details of that error message:
https://www.twilio.com/docs/api/errors/30007
I suspect it's because the message includes a Bitly URL shortener link (snvl.ly). I've seen SMS carriers deny messages when shortner links are used.
Sun Valley has such a short domain name already (sv.cc), they don't really need to use a shortener service. If this link were taking them to a rock page, you could just use a route, or Rock short link. But because it's a document on their file system, we'd have to create a rock page with a redirect to the document. I did that here: https://rock.sv.cc/page/103?Page=1780
Notice on that page that it has a route of /baptismfaq, and uses a redirect block to redirect to the PDF document. So now they could use this URL in the SMS message: https://my.sv.cc/baptismfaq
which is one character longer than the shortener link they have currently.
*Adding the new links in the text in the workflow, worked