Skip to content

mp-reporting-problem.md

Latest commit

 

History

History
45 lines (32 loc) · 1.78 KB

mp-reporting-problem.md

File metadata and controls

45 lines (32 loc) · 1.78 KB
copyright
years
2020, 2021
lastupdated 2021-01-05
keywords push notifications, push notification, notifications, reporting a problem
subcollection mobilepush

{:external: target="_blank" .external} {:shortdesc: .shortdesc} {:codeblock: .codeblock} {:pre: .pre} {:screen: .screen} {:tip: .tip} {:important: .important} {:note: .note} {:download: .download}

Reporting a problem to the {{site.data.keyword.mobilepushshort}} team

{: #mp-report-problem}

If you're experiencing a problem with {{site.data.keyword.mobilepushshort}}, first check the {{site.data.keyword.cloud_notm}} status page{:external}.

If you'd like help from the {{site.data.keyword.mobilepushshort}} team, gather all the following information. The more information that you can provide upfront, the more efficiently the team can help with the problem: {:shortdesc}

  1. Which {{site.data.keyword.cloud_notm}} location (region) is your instance of {{site.data.keyword.mobilepushshort}} provisioned in? For example, Dallas or London.

  2. When did the problem first occur (specifically time, date, and timezone)? How long was your app running before this?

  3. Is the problem still occurring? Can you replicate it?

  4. What is the appGuid of the {{site.data.keyword.mobilepushshort}} service you are using?

    You can find this ID by looking at the "appGuid" field in the Service Credentials tab. For example:

    "appGuid": "8e54a510-5e90-4bac-8a03-d03511b20510"

  5. Do you have application log snippets that display the problem?

  6. What impact is the problem having on your service?

You can provide the information you've gathered to IBM in a support ticket by submitting a support request{:external}.