Connected Content Order of Operations-- :save :retry :cache_max_age?
Hi all, is there a specific order I need to have :save, :retry, and :cache_max_age in on an API call? Example attached... we're seeing some interesting behavior where cache doesn't seem to be working as intended so want to confirm we have this set up correctly. I can't find any documentation on this in Braze or elsewhere. Thanks!Need Help Troubleshooting Connected Content Call
I'm trying to do a connected content call to the Trustpilot API so that I can get back an individualised URL for a customer to submit a trustpilot review:https://documentation-apidocumentation.trustpilot.com/invitation-api#generate-service-review-invitation-link This requires 2 calls, one for the Oauth token and a 2nd to call the endpoint that generates the link. I've been able to successfully do the first call, but having issues with the 2nd, mostly because Braze isn't giving me any feedback. Here is the call (sans sensitive IDs): {% connected_content https://invitations-api.trustpilot.com/v1/private/business-units/xxxxx/invitation-links :method post :headers {"Content-Type": "application/x-www-form-urlencoded", "Authorization": "Bearer {{token.access_token}}" } :body name={{${first_name}}}&referenceId={{${user_id}}}&local='en-US'&email={{${email_address}}} :save result %} {{result.__http_status_code__}} {{result.url}} You can see after the connected call I'm also trying to return the HTTP code and also the expected URL to help with troubleshooting. However, I'm not getting anything returned in those blocks. In addition, the Dev console doesn't seem to be much help because one minute I'll get some feedback (such as a 401 error) in it. The next minute, without changing anything, no errors will show up. And I can't get anything to show up even when I deliberatly try break the connected content call. Any help with better ways to troubleshoot connected content calls or if you can spot any errors in my specific call would be appreciated.
