# Issue with Auth0 Management API: "Request to Webtask exceeded allowed execution time"

**URL:** <https://community.auth0.com/t/issue-with-auth0-management-api-request-to-webtask-exceeded-allowed-execution-time/168845>\
**Category:** Get Help\
**Tags:** actions-management-api, management-api\
**Created:** [January 16, 2025, 6:04am UTC](https://community.auth0.com/t/issue-with-auth0-management-api-request-to-webtask-exceeded-allowed-execution-time/168845 "2025-01-16T06:04:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![foxfoxbee314](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/foxfoxbee314/32/61736_2.png) [@foxfoxbee314](https://community.auth0.com/u/foxfoxbee314)\
**Post date:** [January 16, 2025, 6:04am UTC](https://community.auth0.com/t/issue-with-auth0-management-api-request-to-webtask-exceeded-allowed-execution-time/168845/1 "2025-01-16T06:04:23Z")

</div>

I encountered an issue while using Auth0 with a custom database. When testing the custom database scripts, everything works as expected. Deleting a user via the Auth0 dashboard also works perfectly. However, when I attempt to delete a user using the Management API, I receive the following error:  
`Request to Webtask exceeded allowed execution time.`

Upon investigating the logs, I noticed that the delete user endpoint in my script is only accessed after the error is thrown.

Could you please help me identify what might be causing this issue? Specifically:

1. Why is the delete user endpoint not called immediately?
2. How can I ensure the script executes within the allowed time limit?

Any guidance would be greatly appreciated!

---

<div class="post-metadata">

**Author:** ![sumansaurav](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/sumansaurav/32/70627_2.png) [@sumansaurav](https://community.auth0.com/u/sumansaurav)\
**Post date:** [January 16, 2025, 6:13am UTC](https://community.auth0.com/t/issue-with-auth0-management-api-request-to-webtask-exceeded-allowed-execution-time/168845/2 "2025-01-16T06:13:36Z")

</div>

Regarding why the delete user endpoint isn’t called immediately:

- When using the Management API to delete a user, Auth0 first attempts to perform some internal cleanup operations
- This includes removing the user from any organizations, revoking refresh tokens, and cleaning up any associated data
- Only after these operations complete does Auth0 call your custom database delete script
- If these preliminary operations take too long, the webtask times out before reaching your script

These posts can help you explain why you receiving the error.

[https://community.auth0.com/t/request-to-webtask-exceeded-allowed-execution-time-error-from-authorize-endpoint-or-oauth-token-endpoint/104471](https://community.auth0.com/t/request-to-webtask-exceeded-allowed-execution-time-error-from-authorize-endpoint-or-oauth-token-endpoint/104471)

> [@"Request to Webtask exceeded allowed execution time" for a specific user](https://community.auth0.com/t/request-to-webtask-exceeded-allowed-execution-time-for-a-specific-user/138369):
>
> Hello, I have a specific user who is receiving “Request to Webtask exceeded allowed execution time” errors when attempting to login. After a few tries they got “Your account has been blocked after multiple consecutive login attempts. We’ve sent you a notification via your preferred contact method with instructions on how to unblock it.” Based on this post [“Your Account has been Blocked After Multiple Consecutive Login Attempts” Error](https://community.auth0.com/t/your-account-has-been-blocked-after-multiple-consecutive-login-attempts-error/87776), I had our Dev look into the admin console but could not se…

If the issue persists, you could consider implementing a queue-based system for user deletion, where the Management API triggers a deletion request that gets processed asynchronously, though this would require additional infrastructure.

---

<div class="post-metadata">

**Author:** ![dawid.matuszczyk](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dawid.matuszczyk/32/74550_2.png) [@dawid.matuszczyk](https://community.auth0.com/u/dawid.matuszczyk)\
**Post date:** [January 16, 2025, 11:23am UTC](https://community.auth0.com/t/issue-with-auth0-management-api-request-to-webtask-exceeded-allowed-execution-time/168845/3 "2025-01-16T11:23:36Z")

</div>

Hi @foxfoxbee314,

Welcome back to the Auth0 Community!

Thank you, @sumansaurav, for answering and helping other community members! I would personally add that you can try to debug this using [Real-time Webtask Logs Extension](https://auth0.com/docs/customize/extensions/real-time-webtask-logs).

Thanks  
Dawid

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [February 27, 2025, 4:36pm UTC](https://community.auth0.com/t/issue-with-auth0-management-api-request-to-webtask-exceeded-allowed-execution-time/168845/4 "2025-02-27T16:36:11Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.

---

<div class="post-metadata">

**Author:** ![Tiffani](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/tiffani/32/75235_2.png) [@Tiffani](https://community.auth0.com/u/Tiffani)\
**Post date:** [July 29, 2026, 4:50pm UTC](https://community.auth0.com/t/issue-with-auth0-management-api-request-to-webtask-exceeded-allowed-execution-time/168845/5 "2026-07-29T16:50:09Z")

</div>


