Page MenuHomewrite.as

Track asynchronous errors
Closed, InvalidPublic

Description

  • Add internal interface for adding any errors that arrive (to later show to users)
  • GET /me/errors - fetch list of errors
  • DELETE /me/errors/{id} - error was cleared

Event Timeline

matt created this task.Dec 9 2015, 2:23 AM
matt claimed this task.
matt raised the priority of this task from to Normal.
matt updated the task description. (Show Details)
matt added projects: Restricted Project, API.
matt moved this task to Restricted Project Column on the Restricted Project board.
matt changed the visibility from "All Users" to "Restricted Project (Project)".
matt changed the edit policy from "All Users" to "Restricted Project (Project)".
matt added a parent task: Restricted Maniphest Task.
matt added a subscriber: matt.
matt updated the task description. (Show Details)Feb 3 2016, 10:27 PM
matt lowered the priority of this task from Normal to Low.Jul 6 2016, 11:54 PM
matt closed this task as Invalid.Oct 16 2016, 5:51 PM

The user errors route is the wrong design for these problems. Instead, we need to track successful events, noting any errors that occur along with them. This will work for webhooks, cross-posts, connections to custom publish platforms.

matt changed the visibility from "Restricted Project (Project)" to "Public (No Login Required)".Thu, May 14, 2:50 PM
matt changed the edit policy from "Restricted Project (Project)" to "All Users".