SanfordWhiteman

This is a poor choice of architecture. It has a built-in race condition and isn’t reliable for professional use. It also cuts your sending capacity in half even when it works! If an OAuth token is required, you should send your webhook requests to an intermediate API Gateway service that manages (i....

You’d have to turn off the built-in qualification rule and let people run through every time. Then build an equivalent limitation using, for example, Program Statuses (if the person is already status Sent for a given Program, then Remove from Flow). You don’t change the status for your internal seed...

Doing some of my own tests, think I see the problem(s):“New Outlook” requires a proprietary iCalendar property X-MICROSOFT-LOCATIONSOURCE a proprietary property order not previously required. I should be able to add those to Agical within the next week. Even when you switch to New Outlook, Classic O...

Please provide a link with the tokens actually interpolated — that link will never work because it has the {{token}} placeholders still in it.

@Sant_Singh_Rath and @Ruchi_Lapran1 both your responses are incorrect or incomplete. While it’s true that the rule domain.example will not block 123domain.example, it will block us.domain.example. The rules cover an entire private domain suffix. So if you enter example.com, domains are checked to se...

Indeed, I call it the Fieldset-at-a-Time (FsaaT) method and there’s a blog post and some demos out there. The JS can be even tighter now than a few years ago due to browser built-ins, it’s really quite easy. If you don’t care about giving somebody a Back button, just use multiple forms. The user doe...

@Raul-Ok please return and check responses.

Because I want you to get your forms back in working order sooner than later, let me cut to the direct cause. The 3rd-party Digital Pi tracking JS has a configuration area where you set up mappings between UTM params and form fields. You currently have empty strings for three of these:{ utm_med...

Figured it out after more work. It's actually quite easy to trigger (details to follow) and is due to a glaring bug in some 3rd-party JS. Not a race condition or accidental CORS thing. I'll put the explanation up on the blog and link to it here.