Worked this time. It was a 'failed to resolve domain' error previously so potentially just a blip that was preventing zaps. If it's your domain it might be worth looking into logs. My original note was sent as the issue was occurring.

Reply to this note

Please Login to reply.

Discussion

No replies yet.