# A0deploy cli not changing the status of action scripts from built to deploy

**URL:** <https://community.auth0.com/t/a0deploy-cli-not-changing-the-status-of-action-scripts-from-built-to-deploy/187316>\
**Category:** Get Help\
**Tags:** configuration, application\
**Created:** [May 28, 2025, 11:09pm UTC](https://community.auth0.com/t/a0deploy-cli-not-changing-the-status-of-action-scripts-from-built-to-deploy/187316 "2025-05-28T23:09:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dharihar](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dharihar/32/72989_2.png) [@dharihar](https://community.auth0.com/u/dharihar)\
**Post date:** [May 28, 2025, 11:09pm UTC](https://community.auth0.com/t/a0deploy-cli-not-changing-the-status-of-action-scripts-from-built-to-deploy/187316/1 "2025-05-28T23:09:24Z")

</div>

I am working on setting up the pipeline for writing auth0 scripts and i am seeing an issue where the action scripts created under library remains in `built` state and not changing to `deployed ` even after i used the cli commands `a0deploy ` with` --experimental_ea --force` . Wondering does Auth0 CLI provide an option to explicitly change an action script created from `built` to `deployed` state ?

Seeing the error “Trying to create a binding for an action that has not been deployed yet.”

---

<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:** [May 28, 2025, 11:32pm UTC](https://community.auth0.com/t/a0deploy-cli-not-changing-the-status-of-action-scripts-from-built-to-deploy/187316/3 "2025-05-28T23:32:24Z")

</div>

Hi @dharihar

Welcome to the Auth0 Community!

According to our Knowledge Article on “Trying to create a binding for an action that has not been deployed yet”, the build has most likely not yet finished. Can you try to increase the delay between deploying and trying to assign to up to 2 minutes?

You can read more about that here → [Management API Error "Trying to Create a Binding for an Action That Has Not Been Deployed Yet"](https://community.auth0.com/t/management-api-error-trying-to-create-a-binding-for-an-action-that-has-not-been-deployed-yet/183214)

Thanks  
Dawid

---

<div class="post-metadata">

**Author:** ![dharihar](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dharihar/32/72989_2.png) [@dharihar](https://community.auth0.com/u/dharihar)\
**Post date:** [May 29, 2025, 12:02am UTC](https://community.auth0.com/t/a0deploy-cli-not-changing-the-status-of-action-scripts-from-built-to-deploy/187316/4 "2025-05-29T00:02:56Z")

</div>

Thanks for the reply. Yes, i did added upto 120 seconds delay between by action deploy command and the trigger deploy command. It still did not work

---

<div class="post-metadata">

**Author:** ![dharihar](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dharihar/32/72989_2.png) [@dharihar](https://community.auth0.com/u/dharihar)\
**Post date:** [May 29, 2025, 5:27pm UTC](https://community.auth0.com/t/a0deploy-cli-not-changing-the-status-of-action-scripts-from-built-to-deploy/187316/5 "2025-05-29T17:27:19Z")

</div>

It worked after i mentioned “deployed”:true in the scripts

---

<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:** [June 12, 2025, 5:27pm UTC](https://community.auth0.com/t/a0deploy-cli-not-changing-the-status-of-action-scripts-from-built-to-deploy/187316/6 "2025-06-12T17:27:40Z")

</div>

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