On July 14, 2016 (approx. 5:30 p.m. EDT), we will patch an existing bug affecting user counts for a select number of jobs in the system. User counts will only be affected if they are part of the following job list and the respective profile uses a specific var value number (integer) type as noted below. The …

As first announced in April of this year, API rate limiting restrictions matching our current best practices will be enforced across all applications accessing Sailthru, effective Sept. 6, 2016. This announcement also noted two change milestones at no sooner than 60 and 30 days prior to the September change. On Thursday, July 14, the first planned …

In our continued work to add efficiency to popular jobs, we are releasing a performance enhancement to our List Erase job. Erasing a list using my.sailthru or the API does more than just removes the list from the “Lists” page – we also go through and update every single profile affected by the list removal. We …

Each time you edit and save a template, Sailthru keeps the previous version and makes all previous versions available to you. This helps protect you from accidents and offers a way to trace changes. This functionality is here to stay. However, to prevent the limitless growth of stored revisions, we are putting liberal bounds on it. For each template, at least 40 of your most recent …

On Thursday, July 7, 2016, we will resolve a bug that previously allowed your limited-access users on my.Sailthru.com to schedule campaigns using lists they should not have had access to. When creating or modifying a campaign, limited-access users will no longer be given the option to send to any lists that their team was not …