# 81002: Unexpected event while processing Widget

Log Type: APPLICATION

Log Level: WARNING

## Description

An unexpected event was received while processing a widget. Studio ignored this event and did not transition to another widget because there was no matching transition available to handle the event.

*Note:* If the Execution ended correctly, this warning can be ignored.

### Possible causes

* A new call, message, or REST API Execution was initiated for a contact address (e.g. phone number) that already has an active Execution.
* An event came in while processing a widget that cannot handle that event (e.g. incoming message received during Run Function widget).
* A hangup for a phone call was detected while processing a widget that does not have a "Hangup" transition (e.g. HTTP Request or Send Message).
* There was no transition that matched the received event.

### Possible solutions

* Incoming Calls only: Enable [Concurrent Calls](/docs/studio/user-guide#handling-concurrent-calls-from-the-same-number-in-studio) in the Flow's Trigger widget.
* REST API-triggered Executions: Use [Studio REST API v2](/docs/studio/rest-api/v2/execution#create-a-new-execution) to create Executions and end any that are still active for the same contact.
* Return results for Function calls and HTTP requests quickly.
* End any [stuck Executions](https://support.twilio.com/hc/en-us/articles/360019383714-Understanding-and-Avoiding-Stuck-Executions-in-Twilio-Studio) via Twilio Console.