tag:status.reply.io,2005:/historyReply Status - Incident History2024-03-29T05:23:33ZReplytag:status.reply.io,2005:Incident/202645442024-03-15T11:29:28Z2024-03-15T11:29:28ZReply Detection Issue<p><small>Mar <var data-var='date'>15</var>, <var data-var='time'>11:29</var> UTC</small><br><strong>Resolved</strong> - We're pleased to announce that the reply detection issue affecting some customers has been successfully resolved. Our team has implemented a fix and all outstanding replies should be detected. <br /><br />We appreciate your patience and understanding throughout this process. If you encounter any further issues, please don't hesitate to reach out to our support team.</p><p><small>Mar <var data-var='date'>15</var>, <var data-var='time'>11:10</var> UTC</small><br><strong>Investigating</strong> - We're currently investigating reports of reply detection issues affecting some customers. <br /><br />We apologise for any inconvenience caused and appreciate your patience as we work to resolve this issue promptly. Further updates will be provided as soon as more information becomes available.</p>tag:status.reply.io,2005:Incident/200869712024-02-27T12:55:30Z2024-02-27T12:55:30ZSequences Not Sending - Investigation Underway<p><small>Feb <var data-var='date'>27</var>, <var data-var='time'>12:55</var> UTC</small><br><strong>Resolved</strong> - Dear customer,<br /><br />We are pleased to update you that the problem with sequences not sending, accompanied by the "Planning Cancelled, Waiting for Successful Detection" error, has been fixed.<br /><br />For any remaining concerns, please contact our support team at support@reply.io or via chat.<br /><br />Thank you for your patience.</p><p><small>Feb <var data-var='date'>27</var>, <var data-var='time'>11:17</var> UTC</small><br><strong>Investigating</strong> - Dear customers, <br /><br />We're currently investigating an issue where some sequences are not sending, accompanied by the error message "Planning Cancelled, Waiting for Successful Detection." Our team is actively working on a resolution. Updates will follow.<br /><br />We apologize for any inconvenience.</p>tag:status.reply.io,2005:Incident/185466162023-09-19T15:30:10Z2023-09-19T15:30:10ZSequencing Delays<p><small>Sep <var data-var='date'>19</var>, <var data-var='time'>15:30</var> UTC</small><br><strong>Resolved</strong> - Dear customers,<br /><br />We are delighted to announce that the issue causing delays in the planning and sending of sequences has been successfully resolved. Our dedicated team has worked diligently to rectify the situation and ensure that our services are back to operating at full capacity.<br /><br />We appreciate your patience and understanding throughout this process.<br /><br />If you encounter any unexpected issues or have any questions, please don't hesitate to reach out to our support team in chat or at support@reply.io. We are here to assist you.<br /><br />Thank you for your trust in our services. We remain committed to providing you with the best possible experience, and we look forward to serving you without interruption in the future.<br /><br />Best regards,<br /><br />Reply team</p><p><small>Sep <var data-var='date'>19</var>, <var data-var='time'>15:10</var> UTC</small><br><strong>Investigating</strong> - Dear customers,<br /><br />We want to keep you informed about the current status of our services. At this time, we are experiencing some delays in the processing and sending of sequences. We understand the importance of reliable and prompt service, and we sincerely apologize for any inconvenience this may be causing you.<br /><br />Our dedicated team is actively working to address this issue and restore normal operations as swiftly as possible. We are committed to ensuring that you receive the high-quality service you expect from us.<br /><br />Thank you for your patience and understanding as we work diligently to resolve this matter. If you have any urgent concerns or questions, please don't hesitate to reach out to our support team via chat or at support@reply.io.<br /><br />We appreciate your trust in us, and we will keep you updated every step of the way.<br /><br />Sincerely,<br /><br />Reply team</p>tag:status.reply.io,2005:Incident/171412252023-05-04T09:39:57Z2023-05-04T09:39:57ZOffice Single-Click Account Reconnection Issue<p><small>May <var data-var='date'> 4</var>, <var data-var='time'>09:39</var> UTC</small><br><strong>Resolved</strong> - We are pleased to inform you that the connection issue with Office Single Click and EWS accounts has been resolved. However, if you continue to see errors with your affected accounts, please reconnect them manually.</p><p><small>May <var data-var='date'> 4</var>, <var data-var='time'>08:42</var> UTC</small><br><strong>Identified</strong> - Our users are currently experiencing difficulty reconnecting their Office single-click accounts. We understand the criticality of this issue and have assigned our top engineers to work on resolving the problem.<br /><br />At the moment, we do not have an estimated time for the resolution, but our team is working around the clock to ensure that the issue is resolved as quickly as possible. We will provide further updates on the status page as soon as we have more information.<br /><br />We apologize for any inconvenience this may have caused and appreciate your patience and understanding while we work to resolve this issue.</p>tag:status.reply.io,2005:Incident/165923322023-03-23T16:08:44Z2023-03-23T16:08:44ZLinkedin automation steps issue<p><small>Mar <var data-var='date'>23</var>, <var data-var='time'>16:08</var> UTC</small><br><strong>Resolved</strong> - We are delighted to inform you that the delays in sending automatic LinkedIn steps have been resolved. <br /><br />However, if you continue to encounter any problems, please do not hesitate to contact our support team via chat or email at support@reply.io.</p><p><small>Mar <var data-var='date'>22</var>, <var data-var='time'>15:25</var> UTC</small><br><strong>Update</strong> - We have released an update today that appears to have resolved the issue with automatic LinkedIn steps for some of our customers. <br /><br />However, we have identified a small group of sequences where the planning is taking place but the connections and messages are not being sent. <br /><br />Our team is actively investigating this matter to find a prompt solution.<br /><br />Thank you for your patience and understanding while we are working to resolve the issue.</p><p><small>Mar <var data-var='date'>21</var>, <var data-var='time'>14:39</var> UTC</small><br><strong>Identified</strong> - We are currently experiencing some difficulties with our automatic LinkedIn outreach system. While customers may see that their prospects have been planned, no messages or connection requests are being sent out.<br /><br />Rest assured that we are actively investigating this issue and working to resolve it as soon as possible. <br /><br />Thank you for your patience and understanding.</p>tag:status.reply.io,2005:Incident/162244792023-02-21T18:22:49Z2023-02-21T18:22:49ZDegraded performance with export functionality<p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>18:22</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>17:42</var> UTC</small><br><strong>Investigating</strong> - Dear customers, we are sorry to inform you that export functionality is not operational at the moment. Our team is investigating this case and working to resolve it as soon as possible.</p>tag:status.reply.io,2005:Incident/161768232023-02-17T14:07:30Z2023-02-17T14:07:30ZSome sequences are not sending at their optimal capacity at this time<p><small>Feb <var data-var='date'>17</var>, <var data-var='time'>14:07</var> UTC</small><br><strong>Resolved</strong> - We are pleased to inform you that the issue with intermittent email sending has been resolved. As long as the schedule is open, all sequences should now send at full capacity. Thank you for your patience and understanding.</p><p><small>Feb <var data-var='date'>17</var>, <var data-var='time'>13:42</var> UTC</small><br><strong>Identified</strong> - Dear customers,<br /><br />We understand that some of you have experienced reduced sending capacity for your sequences starting at 9am UTC. <br /><br />Our development team is actively working to address the issue and we appreciate your patience and cooperation.</p>tag:status.reply.io,2005:Incident/159458862023-01-27T10:05:42Z2023-01-27T10:05:42ZEmail delivery delay for Reply Application<p><small>Jan <var data-var='date'>27</var>, <var data-var='time'>10:05</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved. Now all system are operational.</p><p><small>Jan <var data-var='date'>26</var>, <var data-var='time'>21:52</var> UTC</small><br><strong>Investigating</strong> - We apologize for any inconvenience caused by the delay in email deliveries. We are investigating the issue and working to resolve it as quickly as possible.</p>tag:status.reply.io,2005:Incident/159300842023-01-25T11:33:49Z2023-01-25T11:33:49ZService Interruption for Reply Application<p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>11:33</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved. All systems are operational. Have a great day!</p><p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>09:37</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating a degradation of service to the Reply application. Customers may experience issues with logging in, slow loading. Sequences are sending as planned, API and Chrome Plugin are operational</p>tag:status.reply.io,2005:Incident/139259802022-11-29T13:11:46Z2022-11-29T13:11:46ZSequence sending issue since 8:00 am UTC<p><small>Nov <var data-var='date'>29</var>, <var data-var='time'>13:11</var> UTC</small><br><strong>Resolved</strong> - Prospect export with all fields and triggers should be working now</p><p><small>Nov <var data-var='date'>29</var>, <var data-var='time'>11:57</var> UTC</small><br><strong>Identified</strong> - The issue with sending has been identified and resolved. Sequences will send provided the schedule is still open. Prospect export and triggers are still under investigation</p><p><small>Nov <var data-var='date'>29</var>, <var data-var='time'>10:08</var> UTC</small><br><strong>Investigating</strong> - Since approximately 8:00 am UTC we are experiencing interruptions in sending sequence emails. Exporting prospects with all fields and triggers might not be working as well. Our team is already investigating these issues</p>tag:status.reply.io,2005:Incident/115272602022-10-07T07:34:24Z2022-10-07T07:34:24ZCSV Import To A List Results In Removing Updated Prospects From Their Sequences<p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>07:34</var> UTC</small><br><strong>Resolved</strong> - The issue with importing csv into a list has been resolved. If you need help moving the removed prospects back to the sequence, please reach out to us in chats.</p><p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>08:27</var> UTC</small><br><strong>Investigating</strong> - We have received a few reports for when a csv file is imported into the list on People page, prospects that are updated via the csv are removed from their respective sequences. We are looking into this at the moment. If you experienced an issue where prospects were removed from the sequence, please reach out to our support team and we will help you move them back <br /><br />Until the issue is resolved, we do not advise importing csv files into lists directly. Instead, you can filter imported people with "Import file name" parameter and move them to the list manually</p>tag:status.reply.io,2005:Incident/110878892022-09-12T08:24:50Z2022-09-12T08:24:50ZLinkedin Automation: Replies are not detected<p><small>Sep <var data-var='date'>12</var>, <var data-var='time'>08:24</var> UTC</small><br><strong>Resolved</strong> - The issue with reply detection for LinkedIn messages has been fixed and missing replies should have been detected as well. We recommend unpausing sequences to allow detection further</p><p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>10:27</var> UTC</small><br><strong>Investigating</strong> - We are currently experiencing an issue with detecting replies for leads that received messages or connection requests from Reply via LinkedIn Automation steps. According to our knowledge, missed replies might date back to as early as August 30. <br /><br />Our dev team is looking into this with highest priority <br /><br />In order to avoid reaching out to leads that replied, we recommend pausing sequences with automatic LinkedIn Steps</p>tag:status.reply.io,2005:Incident/109489362022-08-26T14:45:37Z2022-08-26T14:45:37ZReply.io - Reports show no data for today, warmup does not send emails<p><small>Aug <var data-var='date'>26</var>, <var data-var='time'>14:45</var> UTC</small><br><strong>Resolved</strong> - Warmup service is live and reports should reflect the actual sending progress as of now. We apologise for the inconvenience caused by this incident</p><p><small>Aug <var data-var='date'>26</var>, <var data-var='time'>13:43</var> UTC</small><br><strong>Investigating</strong> - We are currently experiencing issues with email reports - today's sent emails are not visible there. Warmup service is also temporary not working</p>tag:status.reply.io,2005:Incident/107664932022-08-08T08:29:04Z2022-08-08T08:29:04ZConnecting Hubspot accounts to Reply<p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>08:29</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>13:40</var> UTC</small><br><strong>Identified</strong> - We have found the cause of the issue and due to complexity of the fix the current ETA is Monday</p><p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>12:35</var> UTC</small><br><strong>Investigating</strong> - We are currently experiencing issue with connecting Hubspot accounts through native Reply integration. Customers might see an error - "Couldn’t complete the connection. This install link is no longer valid. Please visit HubSpot's App Marketplace to install this app." <br /><br />Our dev team is already investigating the potential cause of this error</p>tag:status.reply.io,2005:Incident/107090142022-07-28T13:42:52Z2022-07-28T13:42:52ZCSV import is down<p><small>Jul <var data-var='date'>28</var>, <var data-var='time'>13:42</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jul <var data-var='date'>28</var>, <var data-var='time'>13:42</var> UTC</small><br><strong>Update</strong> - Import has been fixed, as well as export with all fields and generating Outbox. If Outbox report in your account seems to be stuck generating for a while, please reach out to our support team in chats to unlock it</p><p><small>Jul <var data-var='date'>28</var>, <var data-var='time'>13:18</var> UTC</small><br><strong>Investigating</strong> - We are currently experiencing issues with csv file import. Our dev team is investigating the cause of the issue at the moment</p>tag:status.reply.io,2005:Incident/99043702022-05-03T19:02:19Z2022-05-03T19:02:20ZSequences are not sending<p><small>May <var data-var='date'> 3</var>, <var data-var='time'>19:02</var> UTC</small><br><strong>Resolved</strong> - The issue seems to be resolved, sequences affected by planning cancelled error should start sending provided the schedule is open</p><p><small>May <var data-var='date'> 3</var>, <var data-var='time'>14:57</var> UTC</small><br><strong>Investigating</strong> - Some sequences might still not be sending with Planning cancelled, waiting for successful detection error in logs</p>tag:status.reply.io,2005:Incident/99024962022-05-03T13:22:31Z2022-05-03T13:22:31ZSequences are not sending<p><small>May <var data-var='date'> 3</var>, <var data-var='time'>13:22</var> UTC</small><br><strong>Resolved</strong> - The issue has been resolved, sequences should be sending as expected</p><p><small>May <var data-var='date'> 3</var>, <var data-var='time'>10:50</var> UTC</small><br><strong>Investigating</strong> - Some customers reported that sequences are not sending for them since 9am UTC, our team is already investigating the cause of the issue</p>tag:status.reply.io,2005:Incident/98112782022-05-03T11:53:35Z2022-05-03T11:53:35ZZapier: New link Clicked trigger issue<p><small>May <var data-var='date'> 3</var>, <var data-var='time'>11:53</var> UTC</small><br><strong>Resolved</strong> - The issue has been resolved. Clicks from sequences with links tracking enabled are triggering the Zap as expected</p><p><small>Apr <var data-var='date'>19</var>, <var data-var='time'>11:41</var> UTC</small><br><strong>Investigating</strong> - Zapier trigger "New link clicked" does not seem to work at the moment. Our team is working on deploying the fix as soon as possible</p>tag:status.reply.io,2005:Incident/98118022022-04-19T18:44:35Z2022-04-19T18:44:35ZSequences are not sending<p><small>Apr <var data-var='date'>19</var>, <var data-var='time'>18:44</var> UTC</small><br><strong>Resolved</strong> - We would like to inform you that this incident has been resolved and all systems are operational now.<br />Please, accept our apologies for any inconvenience caused.</p><p><small>Apr <var data-var='date'>19</var>, <var data-var='time'>14:32</var> UTC</small><br><strong>Identified</strong> - The issue has been identified, it is related to infrastructural problems with out service provider</p><p><small>Apr <var data-var='date'>19</var>, <var data-var='time'>12:58</var> UTC</small><br><strong>Investigating</strong> - We have received repeated reports that sequences are not sending since 12:10 PM UTC today, April 19th. Our dev team is looking into the issue with outmost priority</p>tag:status.reply.io,2005:Incident/93800292022-02-22T13:57:56Z2022-02-22T13:57:56ZReports in beta do not get updated with sent data<p><small>Feb <var data-var='date'>22</var>, <var data-var='time'>13:57</var> UTC</small><br><strong>Resolved</strong> - The issue has been resolved and all reports should be updated with the respective sent amounts</p><p><small>Feb <var data-var='date'>22</var>, <var data-var='time'>12:57</var> UTC</small><br><strong>Identified</strong> - We are experiencing an issue where Reports > Emails in beta do not get updated with the number of emails sent today. Our dev team is already looking into it</p>tag:status.reply.io,2005:Incident/92578522022-02-07T17:09:28Z2022-02-07T17:09:28ZReports in beta are not updating with today's sent emails<p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>17:09</var> UTC</small><br><strong>Resolved</strong> - The cause of the issue has been eliminated, reports data will be fully updated within next 20-30 minutes</p><p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>16:12</var> UTC</small><br><strong>Identified</strong> - Customers with Beta on might notice that Email based reports are not getting updated with actual sending amounts. However, stats within sequences show the correct sent amount. <br /><br />We are working on resolving the issue with highest priority</p>tag:status.reply.io,2005:Incident/91851222022-02-07T12:40:03Z2022-02-07T12:40:03ZHubSpot native integration - duplicated events<p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>12:40</var> UTC</small><br><strong>Resolved</strong> - The fix for this issue has been deployed on Friday, February 4th. If you have any recent cases with duplicated evens in Hubspot or any other integration, please reach out to our support team in live chat or at support@reply.io</p><p><small>Jan <var data-var='date'>28</var>, <var data-var='time'>15:12</var> UTC</small><br><strong>Investigating</strong> - We have received a few reports on HubSpot events being duplicated with our native integration. So far we have seen a few cases where emails synced with "Emails in Reply > Contract logged email in HubSpot" were recorded several times in contact activity. <br /><br />This does not seem to be a massive occurrence, however, if you noticed duplicated emails in contact profiles on HubSpot side, we recommend turning off the email integration step and setting up BCC instead until the issue is resolved.<br /><br />If you have any questions or concerns, please address them in our live chat or over support@reply.io</p>tag:status.reply.io,2005:Incident/92381562022-02-07T12:26:04Z2022-02-07T12:26:04ZAPI and Zapier errors<p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>12:26</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>16:43</var> UTC</small><br><strong>Update</strong> - API and Zapier issue has been resolved. You might need to run "retry" on stopped Zaps manually to make sure all data in Reply is updated</p><p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>16:10</var> UTC</small><br><strong>Identified</strong> - We are experiencing some issues with API at the moment. <br /><br />POST requests for adding prospects are failing if timezone field is not added in API request. GET requests are also failing with 500<br /><br />For Zapier, creating/updating prospects is impossible without timezone field data as well. We recommend pausing Zaps until the issue is resolved</p>tag:status.reply.io,2005:Incident/92041942022-02-01T10:04:42Z2022-02-01T14:47:39ZReports, prospect's activity and branded links<p><small>Feb <var data-var='date'> 1</var>, <var data-var='time'>10:04</var> UTC</small><br><strong>Resolved</strong> - Adding branded links and prospect activity scrolling are fixed now as well</p><p><small>Jan <var data-var='date'>31</var>, <var data-var='time'>21:22</var> UTC</small><br><strong>Update</strong> - The issue with Reports not showing today's data has been resolved</p><p><small>Jan <var data-var='date'>31</var>, <var data-var='time'>16:20</var> UTC</small><br><strong>Investigating</strong> - We are experiencing a few issues at the moment:<br /><br />1) Reports > Emails page is not updating with today's sent numbers. The accurate sending data is only visible within sequence Stats page<br /><br />2) Prospects activity page is not scrollable <br /><br />3) Adding branded links gives "something went wrong" error <br /><br />We are looking at those issues with top priority</p>tag:status.reply.io,2005:Incident/81226822021-09-30T16:18:11Z2021-09-30T16:18:11ZReply detection issue<p><small>Sep <var data-var='date'>30</var>, <var data-var='time'>16:18</var> UTC</small><br><strong>Resolved</strong> - Starting from Tuesday, September 28th we received a few reports of some replies not being detected. The issue has been resolved for all replies to emails sent starting from September 30th. If a reply has not been detected within 24h, we recommend making such prospect as Replied manually to avoid future correspondence. <br /><br />If you have any questions or need help, please contact our support team in chats or at support@reply.io</p>