This article lists the messages you can see while setting up and running Package Builder, grouped by where they appear. For each message you get the cause and what to do. Messages are quoted as they appear, so you can search this page for the text you see. Text in angle brackets, such as <Add-on>, is filled in for your package. <Add-on> is always the template's Add-On value, such as XL Docs, and <Record ID#> is the template's Record ID# in the Document Templates table.
Where messages appear
Where | What it looks like |
|---|---|
Progress window | The pop-up that opens when a user selects Process Package. Its header is Package Builder. While the package runs, the heading is Generating your Package. When it ends, the heading changes to Your package is ready! or Something went wrong., followed by the message. The Details table lists each step with its Status, Template, Template #, Document Type, and Process Time. See Run a package from a button. |
Status field | The Package Builder Status field on the master record (the stsfid parameter). Every run, from the button or in the background, ends with a message and the date and time, for example Process Successfully Completed on 10/6/2026 2:15:07 PM. This is the only place background runs report their result. See Run details and status. |
The step's own extension | When a step fails, Package Builder reports which step failed, not why. Some extensions write their own reason to a field on the record. See A step failed: where that extension records why. |
Process Package field | The Process Package (Progress Bar) field on the record shows a message instead of the button until the setup is finished. |
Installation wizard | The Package Builder Setup step of the installation wizard. See Package Builder Setup. |
Progress window: status messages
Message | Meaning |
|---|---|
Generating your Package / Please do not close this window while the process runs. | The package is running. The progress bar has one segment per step. Keep the window open: the window starts each step, so closing it stops the steps that haven't started yet. The step that was already running still finishes on our server. If it was the last step, or a required step that failed, the status field and Run Details are still written; otherwise they may not be updated for that run. |
Now Generating: <Name> (#<Record ID#>) or Now Generating: <Add-on> - Template #<Record ID#> | The step that's running, with the percentage of the package done. <Name> is the template's Name; the second form is used when the template record has no Name. |
Your package is ready! / Successfully processed <N> templates. / You may now close this window. | The package finished. N is the number of steps that succeeded, including a Document Merge step. Steps that weren't required and failed are shown in red in the Details table and listed in the status field. |
Something went wrong. / We've run into an error while generating your package: followed by a message | The package stopped. Look up the message that follows in the tables below. |
Details table colors and TBD | Blue is the step that's running, green finished, red failed, and grey not run yet. Process Time shows TBD until the step finishes. Template # shows N/A for the Document Merge step that mergeargsfid adds. |
Progress window: errors
Message | Cause | What to do |
|---|---|---|
The parameters are invalid. Please contact your app administrator. | A required parameter is missing or empty: clientid, appid, dbid, msid, tpdbid, pckgsq, or stsfid—or, in repository mode, rpdbid, rprelfid, or rpfafid. | Check the button formula against Formula URL parameters. Make sure the fields the formula uses—especially Package Builder Template Sequence—aren't empty on this record. |
The package template sequence was empty. Please ensure there is a template sequence provided. | The sequence has no steps that can run. | Fill in Package Builder Template Sequence with template Record ID#s separated by periods. Static Document and Dynamic Document steps run only in repository mode, so a sequence of only those steps has nothing to run in regular mode. |
Template #<Record ID#> has no Add-on selected. Please select an Add-on for this template. | The template's Add-On field is empty. | Open that Document Templates record and choose the extension in Add-On. |
Template #<Record ID#> has an invalid Add-on selected. Please select a valid Add-on for this template. | The Add-On value isn't one Package Builder recognizes. The value must match exactly, including capitals. | Choose Exact Forms Plus, XL Docs, PDF Stamper, or PDF Merger (or, in repository mode, Static Document or Dynamic Document). The older values EFP Batch, XL Docs Batch, PDF Stamper Batch, and PDF Merger Batch also work. If someone added choices to the field, check their spelling. |
We've encountered an error processing this package. Please reach out to your app admin. | The package's templates couldn't be loaded—for example a Record ID# in the sequence doesn't exist in the Document Templates table, tpdbid names a different table, or the Document Templates table is missing the Add-On or Arguments FID field. | Check each Record ID# in the sequence against the Document Templates table, check tpdbid, and check that each template has Add-On and Arguments FID filled in with a field that exists on the master table. |
<Add-on> - Template #<Record ID#> was required but failed to generate. For the automatic final merge: PDF Merger was required but failed to generate. | A required step's extension reported that it failed, so the package stopped. A common cause is that the step's arguments don't pass that extension's own batch configuration—for example after you changed its faid or added repository or merge options. | Find the extension's own reason; see A step failed: where that extension records why. Check that the template's arguments field isn't empty on this record, that it includes that extension's configid=, and that the values are allowed by that extension's configuration (see Each step's own batch configuration). If the package can go ahead without this document, make the step not required (:u in the sequence, or Not Required in Package). |
An unexpected error occurred while generating your package. Please contact your app administrator. | A step failed without a more specific message. | Try once more. If it comes back, check the step as in the row above, then submit a technical support case. |
Package Builder took too long to respond - please refresh to try again, or contact your app administrator. | One step took more than 5 minutes. | Reduce what that step creates (for example fewer records in its query), or run the package in the background, which has no time limit per step. |
No Package Details found - your session may have expired. Please refresh the page. | The window lost track of the package, usually because it sat open and idle for a long time. | Close the window and select Process Package again. |
Unable to get package details. Please contact your app administrator. | The window couldn't load the package's steps when it opened. | Close the window and select the button again. If it continues, submit a technical support case. |
Unable to get running package details. Please contact your app administrator. | The window lost its connection to Package Builder while a step was running. | Check your network connection, then run the package again. Check the status field and the documents before you rerun, so you know which steps finished. |
Any other text, such as a technical error name followed by a description | Something went wrong that Package Builder doesn't have a specific message for. In repository mode with document counting (rdnumfid), this can be one of the counting messages in the next table. | Look the text up in Status field messages. Otherwise try once more, and if it comes back, submit a technical support case with the exact text. |
Status field messages
Background runs report only here. Button runs write the same Process Successfully Completed and Error Encountered messages; the Package builder failed messages and batch configuration messages appear only for background runs.
Message | Cause | What to do |
|---|---|---|
Process Successfully Completed on <date and time> | Every required step succeeded. If lines like Error Encountered on <Add-on> - Template # <Record ID#> follow, those steps weren't required and failed; their documents are missing from the package. | Nothing, unless lines follow. For each line, find that extension's own reason; see A step failed: where that extension records why. |
Error Encountered on <Add-on> - Template # <Record ID#> on <date and time> | A required step failed and the package stopped there. For the merge step that mergeargsfid adds, the message is Error Encountered on PDF Merger on <date and time>, with no Template #. | Find that extension's own reason (see A step failed: where that extension records why), and check its arguments and batch configuration. For the automatic merge, check the PDF Merger arguments field and Merger Error Details. |
Package builder failed. Error details : <detail> on <date and time> | A background run stopped before or between steps. The detail says why—see the rows below. | Fix the cause and request the run again. |
Detail: Template #<Record ID#> has no Add-on selected. Please select an Add-on for this template. | That template's Add-On field is empty. | Open that Document Templates record and choose the extension in Add-On. |
Detail: Template #<Record ID#> has an invalid Add-on selected. Please select a valid Add-on for this template. | That template's Add-On value isn't one Package Builder recognizes. | Choose a valid value, spelled exactly—see the progress window row for invalid Add-on above. |
Detail: Template selected with empty tool name. | A Record ID# in the sequence doesn't exist in the Document Templates table, while other Record ID#s in the sequence do. | Check each Record ID# in Package Builder Template Sequence against the Document Templates table. Remove or correct the one that isn't there, for example a template that was deleted. |
Detail: No rows are returned from Template table. please check there are Package Builder Template is checked properly | None of the Record ID#s in the sequence were found in the Document Templates table. | Check the sequence and tpdbid. |
Detail: Column '<name>' does not belong to table | The Document Templates table is missing a field Package Builder needs, or it has been renamed—for example Arguments FID or Add-On. | Add the field, or change its label back to Add-On or Arguments FID. |
Detail: Couldn't find the query criteris from the arguments., Couldn't find the apptoken from the arguments passed in, or Couldn't find the DBID from the arguments passed in | Document counting (rdnumfid) is on in repository mode, and a step's arguments don't say which records (msid=, msqry=, or msqid=), which app token (a non-empty apptoken=), or which table (dbid= or msdb=) it uses. | Add the missing parameter to that step's arguments, or remove rdnumfid. See Count documents. |
A batch configuration message followed by on <date and time> | A background run's arguments didn't pass Package Builder's batch configuration check, so nothing was created. |
A step failed: where that extension records why
Package Builder runs each step's extension in batch and only learns whether the step worked. The reason a step failed—or why its document wasn't created—is recorded by that extension, if at all. This is also where you see a step that didn't pass its own extension's batch configuration.
Extension | Where it records why | What to do |
|---|---|---|
Exact Forms Plus | The EFP Batch Trigger - Msg Field on the master record. The text starts with ERROR ENCOUNTERED_ and the date and time, followed by the message. | Read the field on the record, fix the step's arguments or the Exact Forms Plus configuration, and run the package again. |
XL Docs | The field named in xldbtfld, on the record named in xldbrid of the table in xldbdbid—but only when the step's arguments include all three. The single-record setup the XL Docs wizard creates doesn't add them, so by default XL Docs doesn't record the reason anywhere in your app. | Create the document with the XL Docs button on the same record to see its message. To have batch runs record it, add xldbdbid= (the master table's ID), xldbrid= (the record's Record ID#), and xldbtfld= (the field ID of XL Docs Batch Trigger Field) to the step's arguments—after you allow that xldbdbid value in the XL Docs configuration, which allows only an empty value as the wizard creates it. See XL Docs batch processing. |
PDF Stamper | Nowhere in your app. | Create the document with the PDF Stamper button on the same record to see its message, and check the step's arguments against the PDF Stamper configuration. If you can't find the cause, submit a technical support case. |
PDF Merger | The Merger Error Details field on the master record. For example, a batch configuration failure starts with Error occured merging documents -. | Read the field, fix the PDF Merger arguments or configuration, and run the package again. |
For which values each extension's configuration allows, see Each step's own batch configuration and Extensions that check batch configurations.
Authorization messages
These appear in the progress window when Package Builder can't confirm that your account and app may use it. A background run with the same problem doesn't start.
Message | Cause | What to do |
|---|---|---|
Quickbase Application - <app ID> is not authorized to use Package Builder. … There is no valid authorization record for client id: <Client ID> … Please contact your Quickbase support representative for more information. | No authorization matches this Client ID and app ID for Package Builder. | Check clientid and appid in the formula—the app must be the one Package Builder was set up in. See Find your Client ID, table IDs, and field IDs. If they're right, submit a technical support case. |
Your Quickbase application - <app ID> is Not authorized to use Package Builder. followed by more detail | The app's authorization for Package Builder isn't active. | Submit a technical support case with the full message. |
A user token is required to execute Package Builder. We currently do not have a user token on file for your account. | Package Builder works with a Quickbase user token saved for your account, and there isn't one. | Add a user token for your account—see Authorization. |
… User token ending with <last characters> on the client profile is invalid. Please provide the valid user token. | The saved user token no longer works—for example it was deleted, or its user was deactivated. | Save a current user token for your account—see Authorization. |
We do not have sufficient permission to execute this add-on with the user token that we have on file ending with <last characters> - <detail> | The saved user token's user can't access this app or one of its tables. | Give that user access to the app and the tables the package uses, or save a token for a user who has it. |
Unable to get authorization details. Quickbase Rate Limit Error Code : 429 | Too many requests reached Quickbase at once. | Wait a minute and try again. |
A message ending Unknown Error code : 500 | The authorization check couldn't be completed. | Try again in a few minutes. If it continues, submit a technical support case. |
Temporary token messages
If your account uses enhanced security, the button must post a temporary token that shows the user can see the master record. These messages appear in the progress window when that check fails. See Enhanced security overview.
Message | Cause | What to do |
|---|---|---|
A temporary authorization token is required for this application. Please check your field settings or contact an App Administrator. | The request had no temporary token—usually because the button isn't the enhanced security button, or the URL was opened some other way (copied, bookmarked, or opened in a new tab). | Use a Formula - Text field with Allow some HTML tags turned on, whose link has OpenAsPopup POSTTempToken and data-temptokendbid, as in Formula URL parameters, and start the package from the button in Quickbase. |
One of the DBID Parameters are missing and is required to check temporary authorization. … | dbid is missing, so the token can't be checked. | Add dbid to the button formula. |
The RecordID parameter is missing and is required to check temporary authorization. … | msid is missing, so the token can't be checked. | Add msid to the button formula. |
Your temporary authorization token does not have access to the requested record. Please contact an App Administrator if you believe you should have access to run this tool. | The user can't view the master record, or data-temptokendbid names a different table than dbid. | Check the user's permission to view the record. Make data-temptokendbid and dbid name the same table (for example Dbid() for both). |
Your temporary authorization token has expired. Please try again or contact an App Administrator. | Temporary tokens are short-lived, and this one ran out—for example the window was reloaded later. | Close the window and select the button again. |
Your temporary authorization token is not authorized to run this tool. If you believe you should be able to, try again from Quickbase or contact your app administrator. | The token doesn't match this request—for example it was created for a different table. | Check that data-temptokendbid names the same table as dbid, then select the button again from Quickbase. |
Something went wrong when we checked your temporary authorization - <detail> or … Please try again or contact an App Administrator. | The token check couldn't be completed. | Try again. If it continues, submit a technical support case with the detail. |
We were unable to get your temporary authorization details. Please contact an app admin. | An unexpected error happened during the token check. | Try again. If it continues, submit a technical support case. |
Batch configuration messages
Batch configuration checking is on for every account, and two kinds of configuration are involved:
Package Builder's own configuration, named by configid in Package Builder Batch Arguments. It's checked for background runs only; the button doesn't check it. When the check fails, no documents are created and the message below, followed by on <date and time>, is written to the status field.
Each step's own extension configuration, named by the configid= in that step's arguments field. Each step runs its extension in batch, so it's checked from the button and in the background. When it fails, the status field and progress window show only that the step failed; the extension records the message itself, if at all (see A step failed: where that extension records why).
See Use a configuration in batch runs.
Message | Cause | What to do |
|---|---|---|
No parameters passed in for batch configuration to process. | The request reached Package Builder without arguments. | Check that the email notification's message contains the Package Builder Batch Arguments field and that the field isn't empty on the record. |
No ConfigID was passed in. This configuration requires a ConfigID. | The arguments have no configid=. | Add configid=<your Config Key> to the batch arguments. |
Could not find a Config with ConfigID <key> - this configuration requires a ConfigID. | No configuration has that key—it's mistyped, shortened, or the configuration was deleted. | Copy the full Config Key from the Batch Config Portal and paste it into configid=. |
Encountered duplicate parameter [<name>] | A parameter the configuration checks appears more than once in the arguments. | Remove the extra copy. |
The following parameters do not match the configuration: [<names>] | Those parameters' values aren't among the configuration's allowed values. Values are case-sensitive and must match exactly. The wizard's configuration for Package Builder checks clientid and appid. | Correct the arguments, or update the allowed values in the Batch Config Portal. See Create and manage batch configurations. |
Setup messages
Message | Cause | What to do |
|---|---|---|
This application does not currently have any of our Document Generation add-ons installed. Please install one of our Document Generation add-ons before attempting to install Package Builder. | Installation wizard. The app has no Document Templates table yet. | Install Exact Forms Plus, XL Docs, or PDF Stamper in the app first, then run the Package Builder wizard again. |
Please select a table you would like to set up with Package Builder. | Installation wizard. No table was chosen in Select Table to Setup. | Choose the master table, then select Next. |
Please check the checkbox to show that you have read our message on the setup details. | Installation wizard. I understand the above message isn't checked. | Read the message, check the box, then select Next. |
The usertoken selected does not have permissions to create fields in the <table> table. Package Builder needs permissions to create fields in order to continue the setup. | Installation wizard. The user token chosen on the wizard's Authorization step can't create fields in the table you selected, or in the Document Templates table. | Give that token's user permission to create fields in both tables, or go back to Authorization and choose a token whose user has it. |
Template List not set. Please finish the setup for this Package Builder. | The Process Package (Progress Bar) field shows this in place of the button while Package Builder Template Sequence is empty on the record. | Fill in the Package Builder Template Sequence formula with your template Record ID#s. See Set up a package. |
Emails and background requests
Package Builder doesn't send emails. A background run reports its result only in the status field (and the Run Details table, if you use one). Your own Quickbase email notification starts the run; the installation wizard doesn't create it for you.
Problem | Cause | What to do |
|---|---|---|
A Notification Error when you save the email notification, saying the account may only send email to verified Quickbase users | Your Quickbase account can't send notifications to addresses outside your users, and the Package Builder request address is outside them. | Submit a technical support case to allow your account to send emails to non-registered Quickbase users. |
The status field never changes after a run is requested | The request didn't reach Package Builder, or the run didn't start. | Check, in order: the notification fired (add your own address while testing); it sends to the right address with the matching type=—packagebuilder@mail.quickbasetools1.com with type=packagebuilder (US), or packagebuildereu@mail.quickbasetools.com with type=packagebuildereu (EU); the message contains only the batch arguments; every required parameter is there; and the same package runs from the button. If all of that is right, submit a technical support case. |
Only some records got a run after a Grid Edit or import | When several records change in the same action, Quickbase sends the notification's Multiple record version. If it doesn't repeat the arguments once per record, the records aren't requested separately. | Set up the multiple record version as in Create the email notification. |
The status field shows a batch configuration message | The arguments didn't match Package Builder's batch configuration. |
Other problems
Problem | Cause | What to do |
|---|---|---|
The progress window doesn't open, or opens blank | Package Builder can't be shown inside a frame on another page; it must open as a pop-up or in its own window. The browser may also be blocking pop-ups. | Use the button with OpenAsPopup, and allow pop-ups for your Quickbase realm. |
A step succeeds but its document isn't where you expected | Each extension saves its document wherever its own arguments say. | Check that extension's arguments field on the master record. |
A step fails, or its document is missing, after you changed its arguments | The new values aren't allowed by that extension's own batch configuration—for example a new faid, or added repository or merge options. | Add the new values to that extension's configuration in the Batch Config Portal. See Each step's own batch configuration. |
The merged PDF is missing documents or has them in the wrong order | PDF Merger's own arguments decide which files it merges and in what order. | Make sure the merge is the last step, and see Merge a package into one PDF. |
The progress window was closed early, and the status field didn't change | From the button, the window starts each step. When it's closed, the step already running still finishes, but the steps after it don't run, and the status field and Run Details are written only if that was the last step or a required step that failed. | Run the package again and keep the window open until it finishes, or run it in the background. |
Records in the repository table disappeared | In repository mode, Package Builder deletes the master record's repository records before each run by default. | Use rpaqry or rppurgemode to keep them. See Repository mode. |
A Static Document or Dynamic Document step doesn't run | These steps work only in repository mode. | Add rpmode=y and the other repository parameters. |
A setting has no effect, with no error | Parameter names that Package Builder doesn't recognize are ignored. | Check the spelling of the parameter name. |
When to submit a technical support case
Submit a technical support case when:
A message tells you to contact your Quickbase support representative, or an authorization message continues after you've checked clientid, appid, and the user token.
The same unexpected error comes back after you try again.
Your account needs permission to send email notifications to non-registered Quickbase users.
A background request never updates the status field, and you've checked everything in Emails and background requests.
Include the exact message, the time it happened, the app and the master record's Record ID#, whether you used the button or a background run, and the button formula or batch arguments. Remove any app tokens before you send them.
Frequently asked questions
Why does the record show "Template List not set" instead of the button?
Package Builder Template Sequence is empty on that record. Set its formula to the template Record ID#s, separated by periods. See Set the sequence.
How do I find out why a step failed?
Package Builder only reports which step failed. The extension records the reason, if at all: Exact Forms Plus in EFP Batch Trigger - Msg Field, PDF Merger in Merger Error Details, XL Docs only if you add its trigger field parameters, and PDF Stamper nowhere in your app. See A step failed: where that extension records why.
Why does a step fail after I change its arguments?
Each step is checked against its own extension's batch configuration. The configurations the Exact Forms Plus, XL Docs, and PDF Stamper wizards create allow only their own output field in faid and no repository or merge options other than the ones you chose in that wizard. Add the new values to that extension's configuration in the Batch Config Portal before you run the package. See Each step's own batch configuration.
Do button runs need a Config Key?
Not for Package Builder itself: the button doesn't check Package Builder's configuration, so it has no configid. Each step does: every step's arguments need that extension's configid=, from the button and in the background.
Which configuration does "The following parameters do not match the configuration" mean?
Package Builder's own, named in Package Builder Batch Arguments. A step's configuration failure doesn't appear in the status field; you'd see Error Encountered on <Add-on> instead. See Batch configuration messages.
What should I check if the status never changes after I request a background run?
Work through the checklist in Emails and background requests. Most often the notification didn't fire, or the address and type= are for different regions.
Where do I find my Client ID, a table ID, or a field ID?
See Find your Client ID, table IDs, and field IDs.
Can Package Builder use my bulk setup of Exact Forms Plus, XL Docs, or PDF Stamper?
No. A bulk setup keeps its arguments on a separate Batch Processing table, and Package Builder reads each step's arguments from the master record. Set the extension up for single-record generation on the master table. See Before you start.
Can I build packages for many records at once, or from Quickbase Pipelines?
Yes, with background runs. Package Builder has no Pipelines step, but a pipeline, a Grid Edit, or an import can set the request text on many records, and each record gets its own run. See Run packages for many records.
Do I need PDF Merger?
Only if you want one merged PDF. Without it, Package Builder still creates every document; they stay separate. See Merge a package into one PDF.
Why didn't the status update after I closed the window?
The window starts each step. If you close it, the step already running finishes, but the rest don't run, and the status is written only if that was the last step or a required step that failed. Keep the window open, or run the package in the background.
Can a step run more than once in a package?
Yes, in regular mode: put each run's arguments on its own line in the step's arguments field. In repository mode the whole field is one run. See Write each arguments field.
Can I add a cover page or terms and conditions that no extension creates?
Yes, with a Static Document step (the same file every time) or a Dynamic Document step (a file from the record). Both work only in repository mode. See Static Document and Dynamic Document steps.
Which time zone is the date and time in the status field?
Our server's local time, when the run ended. It may not match your time zone.
What can I do when the window says "Package Builder took too long to respond"?
From the button, each step must finish within 5 minutes. Reduce what the step creates, or run the package in the background, which has no per-step limit.