Skip to main content

Crashes - Mark Resolving

Endpoint

/i/crashes/resolving

Overview

Marks crash groups as actively being resolved (is_resolving=true).

Authentication

Countly API supports three authentication methods:

  1. api_key=YOUR_API_KEY
  2. auth_token=YOUR_AUTH_TOKEN
  3. countly-token: YOUR_AUTH_TOKEN

Permissions

Requires crashes Update permission.

Request Parameters

ParameterTypeRequiredDescription
api_keyStringConditionalRequired if auth_token is not provided.
auth_tokenStringConditionalRequired if api_key is not provided.
app_idStringYesTarget app ID.
argsJSON String (Object)YesAction payload.
args.crashesArray of StringsNoCrash group IDs.
args.crash_idStringNoSingle crash group ID.

Provide args.crashes or args.crash_id.

Response

Success Response

{
"result": "Success"
}

Response Fields

FieldTypeDescription
resultStringSuccess when resolving flag update path runs.

Error Responses

  • 400
{
"result": "Please provide args parameter"
}

Standard auth/permission errors from update validation can also be returned.

Behavior/Processing

  • Resolves crash IDs from args.crashes or [args.crash_id].
  • Sets is_resolving=true for matched groups.
  • Emits crash_resolving system log action for each processed crash entry.

Database Collections

CollectionUsed forData touched by this endpoint
countly.app_crashgroups{appId}Crash statusUpdates is_resolving=true.
countly.systemlogsAudit trailReceives crash_resolving action(s).

Examples

/i/crashes/resolving?api_key=YOUR_API_KEY&app_id=6991c75b024cb89cdc04efd2&args={"crashes":["crash_group_1","crash_group_2"]}

Last Updated

2026-03-07