November 3rd, 2020
Vero 1.0
Fixed
Here's a few bugs we've fixed in the last two weeks.
Preheader cloning - A bug has been resolved where existing preheader text was not copied when cloning a campaign.
Multi-language campaign attachments - We've fixed a bug where in some cases the default language attachment was applied instead of a language-specific attachment.
Searching for customers - Fixed an edge case where search results were not always being correctly returned when multiple searches were performed in succession.
October 13th, 2020
Vero 1.0
Fixed
Here's a short list of bug fixes we've made in the last two weeks:Bulk exporting workflow reports - We have resolved an issue that caused bulk exporting the statistics from large amounts of workflows to fail.Vero JavaScript library - We deployed a minor update to our Vero JavaScript library last week to correct a bug where certain special characters were not encoded correctly in a cookie.Push newsletter segment conditions - We have fixed an edge case where segment conditions used in the "At Least" section of Push newsletter were not processed correctly.
September 14th, 2018
Vero 1.0
Fixed
A quick update with some of the bug fixes that have gone live over the last two weeks:
Uploading images when editing campaigns. We fixed a bug when uploading images that meant you couldn't Save a campaign, leading to data loss.
CSS tweaks to Workflows. A number of small changes to Workflows prevent edge-cases like long node names and condition blocks, and enable you to scroll through condition search boxes more smoothly.
Removing providers no longer cause errors on old newsletters. Removing an email delivery provider would cause issues when viewing previously sent newsletters. We've fixed things up so the UI loads correctly.
View Report link not working. The shortcuts to the Reports section were not working properly on the Newsletter overview page, we've fixed this up.
400 errors when tracking data via our API that would mysteriously work with a valid 200 response when retried. We found the root cause and fixed this issue.We're constantly working to fix bugs in response to support queries or QA. Please email us with any bugs you find 🐛. Have a great weekend!