This page includes information on documented bugs or limitations with Engaging Networks. You can find real time updates on incidents and outages on the Engaging Networks Status Page.
Ongoing issues
Status: No known issues
Resolved issues
RESOLVED Some pages and templates containing scripts can’t be saved
🗓️ Impacted timeframe: 3:00 AM ET/ 8:00 AM BST; resolved at 7:30 AM ET / 12:30 PM BST
Issue: We have identified a problem in which templates or pages containing script tags cannot be edited or saved. Pages continued to work as normal from the front end.
🌐 Scope of impact: This was caused by an updated Cloudflare security rule designed to block bad requests to the platform; an exception has now been put in place while still maintaining security.
RESOLVED VGS failed to tokenize credit cards due to AWS outage
🗓️ Impacted timeframe: 3:00 AM ET/ 8:00 AM BST resolved at 6:00 AM ET/ 11:00 AM BST.
12:00 PM ET/ 17:00 BST resolved at 5:45 ET/ 22:45 BST
Issue: Very Good Security (VGS) was impacted by an Amazon Web Services (AWS) outage. That outage caused sporadic issues with credit card tokenization and resulted in new credit card donations not processing for the duration of the outage.
🌐 Scope of impact: This impacted new credit card donations attempted during the AWS outage window. Digital wallet, ACH (bank) and subsequent recurring credit card payments processed without issue.
✅ Not impacted: Digital Wallet, ACH (bank) transactions, and subsequent recurring credit card payments were not impacted and were able to process without issue.
RESOLVED Salesforce Connector did not sync data for accounts in the Canadian datacenter from to
💡Discovery date:
🗓️ Resolution date:
Contact and transactional data for the impacted days was re-synced on as part of the resolution.
Issue: The Salesforce connector did not sync contact or transaction data on or . This was due to an automated job scheduler failing to reboot properly after a maintenance event on . Because of a misconfiguration, alerts were not prompted either.
🌐 Scope of impact: This only impacted clients in the Canadian datacenter using the Salesforce connector. The issue impacted contact and transaction syncs (push and pull).
RESOLVED Tracking parameters on Broadcast Emails, Email (Classic), and Email Marketing Automations are not working in test emails
💡Discovery date:
🗓️ Resolution date:
Issue: Page tracking parameters (
ea.tracking.id) are not being applied to links in test emails. Any transactions made from test emails will not capture the tracking parameter value when the action is completed.
🌐 Scope of impact: This is only impacting test email sends. Tracking parameters are appended as expected for live emails and are captured when the page is submitted.
RESOLVED Salesforce Connector did not sync data for accounts in the Canadian datacenter from to
💡Discovery date:
🗓️ Resolution date:
Contact and transactional data for the impacted days was re-synced on as part of the resolution.
Issue: The Salesforce connector did not sync contact or transaction data on or . This was due to an automated job scheduler failing to reboot properly after a maintenance event on . Because of a misconfiguration, alerts were not prompted either.
🌐 Scope of impact: This only impacted clients in the Canadian datacenter using the Salesforce connector. The issue impacted contact and transaction syncs (push and pull).
Issues are removed after one year