I’ve been working on setting up an automated backup system for our Auth0 configurations, syncing them to GitHub using the Auth0 Deploy CLI (a0deploy). Everything was functioning smoothly up until this morning, when I encountered a new error during the export process.
**Here’s the error message I received:
2024-09-24T09:55:50.588Z - error: Problem running command export
2024-09-24T09:55:50.588Z - error: Problem loading tenant data from Auth0 Forbidden: Th
Has anyone else encountered this error when exporting Auth0 configurations using auth0-deploy-cli? Is it a rate limit issue because we are on a free plan? Due to the structure of our business, it will be challenging for me to provide Auth0 with additional card details.
Any insights or suggestions to help troubleshoot and resolve this issue would be greatly appreciated!
I have an update! It looks like the solution is to include your credit card information in your dashboard settings. This information is only used for verification, and you will not be charged for it.
I have included my credit card information in my dashboard settings. I am still unable to export, however the export error is different now. Here is snippet of the export log file:
a0deploy export --format yaml --output_folder=dev --config_file ./config/dev.json
2024-10-17T17:22:42.474Z - info: Loading Auth0 Tenant Data
2024-10-17T17:22:42.714Z - info: Retrieving rules data from Auth0
2024-10-17T17:22:42.854Z - info: Retrieving rulesConfigs data from Auth0
…
2024-10-17T17:23:10.851Z - info: Retrieving roles data from Auth0
2024-10-17T17:23:11.291Z - error: Problem running command export
2024-10-17T17:23:11.291Z - error: Problem loading tenant data from Auth0 Payment Required: A paid subscription is required for this feature.
The new error is: A paid subscription is required for this feature.
The error logs suggest that the issue is occurring when exporting your role information. The error states that you have Role-Based Access Control configured, but using this feature requires a paid subscription.
Thanks for the update. I disabled RBAC on my API that was using it, but that did not fix the problem. The same error persists.
This is all strange, because before the pricing update in early October, these dev exports were allowed regardless of RBAC usage or plan.
If this helps, these errors are occurring in my Development tenant which is weird because I would expect work in a Development tenant would not be restricted by Free versus Paid plans.
I have deleted all roles from my development tenant. The same error persists.
I am going to need to add them back soon - they are needed during development. IMHO, all paid features should be un-gated during development as they were before the early October 2024 pricing change.
@rueben.tiow, Sorry, I should have tagged you in my last reply.
I tried removing all roles from my tenant and disabling RBAC on my API. The same error " A paid subscription is required for this feature." occurs when try to export via the Auth0 CLI.
a0deploy export --format yaml --output_folder=dev --config_file ./config/dev.json
2024-10-23T08:15:32.474Z - info: Loading Auth0 Tenant Data
2024-10-23T08:15:32.614Z - info: Retrieving rules data from Auth0
2024-10-23T08:15:32.954Z - info: Retrieving rulesConfigs data from Auth0
…
2024-10-23T08:20:15.951Z - info: Retrieving roles data from Auth0
2024-10-23T08:20:15.391Z - error: Problem running command export
2024-10-23T08:20:15.391Z - error: Problem loading tenant data from Auth0 Payment Required: A paid subscription is required for this feature.
(I’ve had to re-add the roles after testing because my apps will depend on them)
IMHO, since any robust development project should place their Action/Triggers source code under external revision control, it is critical for developers to be able to export them via the Auth0 CLI during all stages of their development cycle regardless of their paid subscription status. Can you raise the urgency of this regression up to your product team? Prior to the pricing change, exporting via the CLI was not restricted.
All paid features are un-gated when you have the trial subscription, which lasts for the first 21 days from when you create a tenant. I have verified that your tenants’ trial subscriptions have expired and are now on the free subscription plan. Hence why you are limited to only free features.
I have not been able to determine what is causing this error, which I will escalate to our Engineering teams to get further assistance.
2024-11-05T09:00:10.590Z - info: Retrieving logStreams data from Auth0
2024-11-05T09:00:10.753Z - error: Problem running command export
2024-11-05T09:00:10.753Z - error: Problem loading tenant data from Auth0 Forbidden: There must be a verified credit card on file to perform this operation
I’ve checked and deleted all role data, but the issue is still present. How can I dump my environment?
My export fails on the “Retrieving roles data from Auth0” export step. What is the param name of the paid feature that I need to add to the AUTH_EXCLUDED array to overcome roles data export errors?
@epicpatka , thanks for this suggestion and the link. The export still failed - it was not a problem with roles / RBAC as suggested earlier in this thread.
However, I have discovered the issue
With the list of excluded resource names you provided in the link, I excluded ALL resources. This allowed the export complete to successfully. I then removed the exclusions one-by-one until I found the resource that it fails on:
“AUTH0_EXCLUDED”: [“branding”]
As seen in my CLI logs earlier in this thread, a branding error is not logged. It would be very helpful if the CLI would fail with a log/message indicating which resource is causing the failure.
Here’s the error message I received:
