0

I am getting the following error when clicking a button in an email:

We cannot direct you to the requested web page at this time. Please try again.

The button is linked to a CloudPage in the most common way, using CloudPagesURL: %%=CloudPagesURL(337)=%%. There is nothing unusual happening in the Cloud Page itself, just some simple AMPscript wrapped in a try/catch statement, so it should work no matter what. The Cloud Page has been published and works fine when accessed from the link inside Web Studio -- but, I think the error happens somewhere earlier and upon clicking the button, we don't even get to the Cloud Page.

This is not a VAWP link and it is not in any way connected to a SendLog, so it's not that.

The only thing that comes to my mind, is that it might have something to do with the custom subdomain that we use in the account - but I checked other Cloud Pages and they can be accessed from email without any errors.

Any clues what else could be causing this issue?

Improve this question
9
  • can you post your code? If memory serves me right you need to wrap the cloudpagesURL in a RedirecTo
    – 0xsegfault
    Jul 23, 2019 at 12:49
  • %%=CloudPagesURL(337)=%% - it's as simple as that and I shouldn't have to wrap it in a RedirectTo, it's not dynamically pulled from a Data Extension
    – zuzannamj
    Jul 23, 2019 at 12:53
  • 1
    salesforce.stackexchange.com/questions/196197/…
    – 0xsegfault
    Jul 23, 2019 at 12:54
  • or maybe the service is down
    – 0xsegfault
    Jul 23, 2019 at 12:54
  • 2
    Excuse the dumb question, but have you verified that is the correct CloudPageID?
    – Gortonington
    Jul 23, 2019 at 13:22

1 Answer 1

Reset to default
4

@Gortonington thank you for the hint, turns out that my colleague who created the email, used the ID visible in the URL of the Cloud Page in Web Studio, not the actual Page ID - now we have replaced it and it's working fine.

enter image description here

Conclusion: the error message is displayed when the Cloud Page with the ID that you are trying to redirect to doesn't exist.

Improve this answer
1
  • 2
    Glad you were able to figure it out!
    – Gortonington
    Jul 23, 2019 at 13:42

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .