Console problems
Fix a form that will not publish or reaches no visitors, a missing language, a failed scan, an import that stays off and keys you cannot edit.
Find the problem by what the console shows. Most messages name what is missing; the fixes below say where to add it.
Publish is refused#
What you see: You choose Publish and the console does not publish. It lists what is wrong.
Why it happens: One of three checks failed:
- The form has no purposes.
- The form is shown in India and its notice is missing something. The message lists each item, such as the Complaint link URL, a purpose's Data used or the project's Privacy contact.
- The banner's custom CSS or custom layout cannot be used. The Brand panel shows the problem beside the field.
Fix: Fix each item listed, then publish again. See Publish a version.
A form stays on Waiting for approval#
What you see: After you publish, the form shows Waiting for approval with your name, and visitors still get the old version.
Why it happens: The project requires a second person to publish forms. You cannot approve your own request. Saving the draft again cancels a request that is waiting.
Fix: Ask another person with publish rights to open the form and choose Approve and publish. If you edited the draft since, publish again to send a new request. See Approve a publication.
A language is missing from the banner#
What you see: You added or changed a language, but visitors do not see it.
Why it happens: Only the default language and approved languages are published. A language marked Needs review or Changed since approval is left out. Visitors keep the last published version until you publish again.
Fix: Open the language, read every field and choose its approve button, such as Approve Hindi. Then publish the form. See Translate and approve a language.
Translate stops or leaves fields empty#
What you see: Translate stops with a message that points to Project settings, or some languages come back empty.
Why it happens: The translation service is not ready, or it does not cover the language. Sarvam covers English and the 22 Eighth Schedule languages. It leaves any other language empty. Where the deployment has no Sarvam key, the project needs its own.
Fix: Open Project settings and find Translation. Add an API key, or choose another service for languages Sarvam does not cover. See Set up the translation service.
A published form reaches no visitors#
What you see: The form is published, but no banner shows on the site. The forms list reads No regions chosen, or the preview says This form is not shown here.
Why it happens: A form is shown only where a region rule points at it. A rule that is switched off shows no form to anyone.
Fix: Open Consent forms, select the form and choose Regions at the top. Add a rule for the places it serves. For countries no rule reaches, add Everywhere else. Rule changes take effect straight away. See Choose regions.
A purpose change does not reach visitors#
What you see: You edited a purpose, but the banner shows the old text.
Why it happens: A published version is frozen with its purposes as they were that day. Editing a purpose does not mark the forms that use it as changed.
Fix: Open each form that offers the purpose and publish a new version. See Add purposes.
Visitors in India get a plain banner#
What you see: Visitors in India do not get the itemised purposes, the complaint link or the language chooser.
Why it happens: These follow the rule's Law, not the country. A rule of your own that covers India with another law does not run the checks for India.
Fix: Open Consent forms, select the form and choose Regions at the top. Choose Edit on the rule and set its Law to DPDP. The rule must be Opt-in. See Choose regions.
A scan fails or finds no banner#
What you see: The Latest scan panel shows a reason in place of the figures. Or it says No consent banner was found on the first page, so only first-visit storage was recorded.
Why it happens: The scan could not finish, or the start page does not load the consent script. A scan needs a public address. Only one scan runs for a project at a time.
Fix: Check that the consent script is installed on the start page, then choose Scan again. If every scan fails, ask the people who run your deployment. See Scan your site.
The cookie declaration is empty#
What you see: The declaration panel says Nothing to declare yet.
Why it happens: The declaration lists only cookies and storage keys that have a purpose and are not Ignored. Third-party hosts are not part of it.
Fix: Scan the site first, then give each unclassified item a purpose. See Publish a cookie declaration.
The Import button stays off#
What you see: You choose a property file and Import stays off, with a reason.
Why it happens: The file cannot be imported as it is:
- It is not a property export, or part of it is missing.
- A published version no longer matches its content hash, so its wording changed after export.
- A form's banner styling is not accepted, or a form offers a purpose that is not in the file.
- Records name a form version that is not in the file.
- The key you typed is not valid, or is already used in this project.
Fix: Export the property again, or import without records. Do not edit the file. See Export and import a property.
A property cannot be deleted#
What you see: Delete is refused, and the console says how many forms and keys are left.
Why it happens: A property can be deleted only while no forms or keys belong to it. A revoked key still counts. The console has no control to delete a form or a key.
Fix: None in the console. Only a property that never had a form or a key can be deleted. See Manage properties.
An origin is refused on a property#
What you see: You add an origin to a property and the console refuses it, naming another property.
Why it happens: An origin can belong to only one property. The origin is how a visitor is matched to the right property.
Fix: Remove the origin from the property that is named, then add it here. See Manage properties.
A key cannot be edited or shown again#
What you see: A key has no control to change its name, property, origins or rate limit. A secret key or identity secret is no longer shown.
Why it happens: A key is fixed when it is created. The secret key and the identity secret are shown once.
Fix: Create a new key with the right values, install it, then choose Revoke on the old one. For a lost identity secret, choose Rotate identity. See Manage keys.
Expiring soon still counts 30 days#
What you see: You changed Count as “expiring soon” within, but Records and Overview still count 30 days.
Why it happens: The choice is saved with the project, but the console does not use it. The filter, the amber dates and the expiring figure always count 30 days.
Fix: None. Read the expiry date on each record for other periods. See Change project settings.
Still stuck#
Collect these before you ask for help:
- the exact message the console shows
- the project id, from Scope in Project settings
- the form's name and version, or the key's hint
- the entry in the Audit log, which shows a refused change as Failed with its status