Ongoing [Informative] Problem in creating media message template by Portal blip
Below is information about the reported failure, regarding the disapproval of WhatsApp's media message template when submitted by the blip Portal, with ...
Resolved Blank Ticket history
We identified in our monitoring an issue related to viewing ticket history.
Resolved Portal and Desk degradation
We identified in Monitoring, a degradation (or instability) of the platform
Resolved Broadcast Plugin
We are currently unavailable to send a broadcast by the Portal Plugin. Our team is already working on it and we will give an update soon.
Resolved WhatsApp Button template failure - Facebook
We identified a flaw in the button template in WhatsApp. impact for the customer: For customers who use this button template feature in the flow of smart contact (Bot). Action in progress: In the analysis carried out by the technical team at Take Blip, no evidence of failure in our environment was identified to justify the observed scenario. With the fault logs collected at the WhatsApp Gateway, we triggered our partner Facebook during the night. We are dealing with the card directly with Facebook. We escalated the ticket and we are waiting for the return from Facebook. Follow the link to the Facebook status page (https://status.fb.com/whatsapp-business-api)
Resolved BLiP Outage
We are experiencing an unavailability on our platform. Impact: The smart contacts are unavailable and are not responding in all channels. Our team is already working and we will soon update.
Resolved Permission failure and login limitation - Facebook
We have identified a failure in the active message triggering model on the Blip Portal. Impact: Failure in the creation and visualization of the firing template within the Blip portal. Action: Our technical team has already identified the fault and are working to correct the failure.
Resolved Desk Application Degradation
In our monitoring, we identified a degradation in the Desk. The team is already verifying this degradation.
Resolved [Informative] - Problem in the variables of the custom reply in the Desk service tool
Status Update: Due to an update carried out in the scheduled maintenance window (carried out on April 28, 2020 at around 11: 30 pm) in the Desk application, we had problems when returning the value contained in the variables used in the “Custom reply” within the screen service desk. Impact: In the Desk attendant screen, when using the “custom reply” feature that uses a variable in the text, only the name of the field is returned and not the value of the variable. It is worth mentioning that the impact is low since only one resource is not being filled in automatically, and can be filled in manually. Correction action: Given that the identified failure is due to an update in production Rollback mapping as a solution action. For this specific scenario, the maneuver involves a restart in the Desk Application service. This action may cause an even greater impact if performed during business hours, since disconnection and subsequent connection of all the attendants who are logged in occurs, so it was defined that the rollback will be performed within the maintenance window on today's date (29/04/2021) at 10 pm.
Resolved Degradation Partial
Through our monitoring, we identified a degradation in our platform, causing several slowdowns in usability. Our technical team is already analyzing what is causing the impact of the failure to the customer: Slow platform usability. The failure is intermittent.
Start with a free account that will allow you to monitor up to five services. Sign up via Google, Slack, or email.
There are 1000 services to choose from, and we're adding more every week.
You can get notifications through the mail, Slack or use Zapier or Webhooks to build your workflows.
You'll never be caught by surprise again. Every time there's a problem with one tool, you'll get a notification ASAP.
We're monitoring 1000 services and adding more every week.
IsDown integrates with hundreds of services. Handles the hassle of going to each one of the status pages and manage it one by one.
We also help control how you receive the notifications.
We monitor all problems and outages and keep you posted on their current status in almost real-time.
You can easily get notifications in your email, slack, or use Webhooks and Zapier to introduce the service status in your workflows.
IsDown collects the status from services to help you be ahead of the game.