Troubleshoot Request Limit or Entitlement Errors at Send Now

Distinguish monthly allowance exhaustion, Max user-group restrictions, unhealthy entitlement validation, central authorization failure, and an unavailable Identity Verification entitlement; no invitations are sent when authorization cannot be confirmed.

This guide applies to All plans; sender and administrator and follows the accepted QC Digital Signature 2.0.7 implementation. Where older walkthrough language differs from the current interface or source behavior, use the current QCDS state as the authority.

Before You Begin

Use a published Template and confirm the required Contacts are present before opening the Request workflow.
Finish unsent work in the current browser session. The streamlined flow does not present ordinary new Requests as persistent server-side drafts before Send Now.
Confirm Joomla mail and the current request allowance before production sending so a delivery or entitlement issue is found early.

Step-by-Step Workflow

Reproduce the issue once, if safe, and record the exact QCDS screen/action and visible message or reference.
Check the current QCDS Status page and the owning object (workspace, Template, Request, signer, delivery, or completed artifact) before changing unrelated settings.
Use the narrow test appropriate to the symptom: Joomla mail test, simple PDF, test Contact, provider Test Connection, Scheduled Task health, or entitlement refresh.
Correct only the failing layer and retry the supported action.
Verify the original transaction/evidence remains intact and gather safe non-secret diagnostics if support is still required.

Distinguish monthly allowance exhaustion, Max user-group restrictions,

For new Requests, the central authorization check is synchronous at Send Now. Basic allows 5 and Pro 25 new Requests per UTC month per recognized site/domain; Max and All Access have no QuantaCade plan-level numeric ceiling. The authorization is idempotent for the stable Request identity so retrying the same already-authorized send does not consume the allowance twice. The sender Dashboard usage card is useful account context, but it is not a substitute for the server-authoritative Send Now check.

For Troubleshoot Request Limit or Entitlement Errors at Send Now, verify this behavior using the actual object involved rather than a generic assumption. A global administrator setting, a sender-workspace preference, a reusable Template, and a sent Request have different ownership and history rules. QCDS is intentionally designed so changes for future work do not silently rewrite the evidence of an already-sent transaction.

No invitations are sent when authorization cannot be confirmed

How This Fits into the QCDS Workflow

The Request editor is the boundary between reusable preparation and an immutable transaction. QCDS lets you make Request-specific choices before sending, then freezes the final participants, fields, routing, message source, and other transaction context when Send Now succeeds.

Because Send Now is the transaction boundary, review the entire transaction immediately before sending: people, assignments, routing, expiration, invitation source, verification requirement, and request allowance.

Verify the Result

Request Details shows the expected lifecycle, participant, Timeline, and delivery state after the action.
Provider Test Connection succeeds and a representative Level 2 test follows the expected provider flow.
Status shows the expected Base and Effective tier and no unresolved entitlement-task integrity warning.
A direct follow-up test confirms the change affects future/current workflow behavior without rewriting historical sent Request evidence.

Common Mistakes to Avoid

Following old instructions that require entering a current license key instead of using Authorized Domains.
Starting the one-time Max Preview merely to inspect a feature before you are ready to evaluate it.
Cancelling/recreating an otherwise valid Request just to repair one failed email address.
Leaving transient unsent work and expecting it to appear later as a persistent draft Request.
Treating provider-backed Identity Verification as required for every ordinary secure-link signing workflow.

Troubleshooting

If Level 2 verification fails, use the provider Test Connection and inspect provider/profile/callback configuration; ordinary Level 1 signing and historical evidence should not be reset.
If a paid feature unexpectedly locks, inspect Authorized Domain resolution, Base/Effective tier, and the hourly Entitlement Revalidation task before changing saved configuration.
If the Request is partly successful, preserve it and repair the failed participant/delivery step. Successful links and recorded history should remain usable.

Operational Best Practice

Test meaningful changes with controlled data before relying on them in production. Keep QCDS, Joomla mail, Scheduled Tasks, and entitlement health observable; preserve successful Requests and completed evidence; and make the smallest change that solves the actual problem. For handoff or support, record the QCDS version, relevant Request/Template reference, the exact action taken, and the visible result without including secrets.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDS feature? Visit the QC Digital Signature Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.