GET /api/v2/actions/actions returns 500 Internal Server Error — broken Action Module FK references after deploy-cli import

Get Help
,
1

Hi,

After running auth0-deploy-cli import, the GET /api/v2/actions/actions
endpoint consistently returns 500 Internal Server Error.

(I will share tenant details and specific resource names/IDs via DM.)

Root cause (investigated):
Several actions have stale references to an Action Module that was
deleted during the import process. The deleted module’s FK reference
remains in the actions’ database records, causing a JOIN failure on
the list endpoint.

Evidence:

  • GET /api/v2/actions/actions → 500
  • GET /api/v2/actions/actions?deployed=true → 200 (works for deployed actions only)
  • GET /api/v2/actions/actions?deployed=false → 500
  • POST /api/v2/actions/actions with an existing action name → 409 Conflict
    (actions still exist in DB but cannot be retrieved or updated via API)
  • GET /api/v2/actions/modules → 200, empty list (module was deleted)

What I need:
Please clear the modules field for the affected actions so the
GET /api/v2/actions/actions endpoint recovers.
Or alternatively, provide the action IDs so I can PATCH them myself
via the Management API.

Thank you.

3

Hi @h-furukawa

Welcome to the Auth0 Community!

I understand that you are receiving 500 errors when calling the GET /api/v2/actions/actions endpoint after importing Actions using auth0-deploy-cli.

Please send a DM ( Direct Message ) to @support forwarding all the information provided and confirming the email address of your Auth0 account and the name of the tenant where you are encountering this issue. The DM creates a private conversation where more sensitive details can safely be shared with us for troubleshooting. We will be able to submit a Support case on your behalf to further look into the root cause of this issue.

Looking forward to your DM!

Best regards,
Gerald