Skip to content

add alarms in the :service_unavaliable return response #1736

@sentry

Description

@sentry

This was from slack discussion: https://omgnetworkhq.slack.com/archives/CVCAR51UY/p1596734766005500?thread_ts=1596733773.001600&cid=CVCAR51UY

It seems like the consensus was to add alarm in response?


Sentry Issue: WEBWALLET-11

Error: The server is not ready to handle the request. Check the alarms for more info.
  at new Promise (<anonymous>)
...
(11 additional frame(s) were not displayed)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions