This article lists the messages you can see in the Batch Configuration Portal and the batch configuration errors a batch run can report. For each message you get the cause and what to do. Messages are quoted exactly as they appear, so you can search this page for the text you see. Answers to common questions are in Frequently asked questions at the end.
Available to: all roles that can open My Extensions in the Extensions Portal.
How portal messages appear
If the portal can't show your configurations when it opens, the message appears in place of the Batch Add-Ons list.
Other errors appear in a message box over the portal, with an OK button. Select OK to close it.
When the portal opens
Message | Cause | What to do |
|---|---|---|
You do not yet have any Batch Configurations - please install a batch add-on into one of your Quickbase applications first. | The company you selected has no batch configurations yet. | Set up a batch extension with the installation wizard; the wizard creates the first configuration (except for Image Resizer/Rotator). If you've already set one up, check that you selected the right company in the Extensions Portal. If it still doesn't appear, submit a technical support case. |
No Client ID was supplied. | The portal couldn't tell which company to show. | Close the window and open it again from Quick Links > Batch Configuration Portal. If your Extensions Portal session has ended, sign in again first. |
Could not load your Batch Configurations - please try again or contact support. | The portal couldn't read your company's details or load its configurations. | Close the window and open it again from Quick Links. If the message continues, submit a technical support case. |
Could not reach the server - please check your connection and try again. | Your browser couldn't connect to the portal. This message can also appear when you save a change. | Check your internet connection, then close the window and open it again, or repeat the change. |
Something went wrong - please try again or contact support. | The portal got an unexpected response. This message can also appear when you save a change. | Close the window, open it again, and repeat what you were doing. If it keeps happening, submit a technical support case and say what you selected. |
When you save changes
These messages appear in a message box.
Message | Cause | What to do |
|---|---|---|
Could not save the configuration name - please try again or contact support. | The new name wasn't saved. The previous name is put back in the Name cell. | Select the Name cell and enter the name again. If it keeps failing, close and reopen the portal, then submit a technical support case. |
Could not save the parameter values - please try again or contact support. | The parameter's allowed values weren't saved. The Add/Edit Batch Parameter dialog stays open with your entries. | Select Save again. If it keeps failing, select Cancel, close and reopen the portal, and make the change again. Then submit a technical support case. |
Could not set values for parameter. | The portal couldn't read the values sent from the Add/Edit Batch Parameter dialog. (An empty Parameter Name doesn't cause this message: Save does nothing until you enter a name.) | Select Cancel, close and reopen the portal, and make the change again. If the message continues, submit a technical support case. |
Could not find that configuration - please reload the page and try again. | The portal couldn't tell which configuration you were changing. | Close the window, open it again from Quick Links, and make the change again. |
Could not find Add-on - please contact support. | The portal couldn't find the extension's settings while creating a configuration. | Submit a technical support case with the extension's name. |
Could not create configuration - please contact support. | The new configuration couldn't be created. | Try again with Add New. If it fails again, submit a technical support case with the extension's name. |
The portal saves a configuration's Name automatically when you leave the cell, and a parameter when you select Save. The Add/Edit Batch Parameter dialog needs a Parameter Name before it can save.
Batch configuration errors in batch runs
Every batch run of the extensions that check batch configurations checks its arguments first. When the check fails, the run stops before it does its work and reports one of these messages. Where you see the message depends on the extension; see Where you see a mismatch.
Message | Cause | What to do |
|---|---|---|
No parameters passed in for batch configuration to process. | The run received no arguments to check. | Check that the email notification's message contains the batch arguments field (and nothing else), and that the field isn't empty on the record. |
No ConfigID was passed in. This configuration requires a ConfigID. | The arguments don't include configid= or configkey=. | Add configid= and the full Config Key to the arguments. See Add the Config Key to your batch arguments. |
Could not find a Config with ConfigID <key> - this configuration requires a ConfigID. | No configuration has the key after configid= (or configkey=). Usually the key was copied partly (for example, only the last 8 characters), has extra spaces or characters, or belongs to a different configuration that was replaced. | Copy the full key again from the Batch Configuration Portal and replace the value after configid=. Make sure there's a space before the next parameter and none inside the key. |
Encountered duplicate parameter [<name>] | A parameter that the configuration checks appears more than once in the arguments. | Remove the extra copy from the formula or notification so the parameter appears once. |
The following parameters do not match the configuration: [<name>, <name>] | The listed parameters were passed with values that aren't in their allowed values. Values must match exactly, including upper and lower case. | On the configuration's Configured Parameters screen, compare each listed parameter's Allowed Value(s) with the value in the arguments. If the new value is correct, select Modify and add it. If it isn't, fix the formula or notification. See How parameters are checked. |
Where you see a mismatch
Each extension reports a failed check in a different place. Some don't write anything to your app.
Extension | Where you see the message |
|---|---|
Bulk setup: the Trigger Field on the XL Docs Batch Processing record. Single-record setup: nowhere in your app by default. To see the message on the record, add xldbdbid, xldbrid, and xldbtfld to the XL Docs Batch Processing Arguments. | |
Nowhere in your app. The run stops without writing a status. | |
Distance runs: the QB Maps Distance Status field shows Distance failed to be updated at: <date and time> Error:<message>. Geocoding runs: nowhere in your app. | |
Single-record setup: the EFP Batch Trigger - Msg Field on the record. Bulk setup: the Trigger Field on the Batch Processing record, plus a record in the Batch Processing Logs and Batch Processing Errors tables. The text starts with ERROR ENCOUNTERED_ and the date and time, followed by the message. | |
The JuicedSign Error Details field on the record. The field shows the message on its own. | |
The Merger Error Details field on the record. The message starts with Error occured merging documents -. | |
The Package Builder Status field on the record. The field shows the message, then on and the date and time. | |
Nowhere in your app. The trigger field keeps its Requested value. |
For example, an Exact Forms Plus single-record run with a faid that isn't allowed writes ERROR ENCOUNTERED_, the date and time, and The following parameters do not match the configuration: [faid] into the EFP Batch Trigger - Msg Field.
If a PDF Stamper or Image Resizer/Rotator run, or a QB Maps geocoding run, does nothing and writes no status, check its batch configuration first: compare the arguments field on the record with the configuration's allowed values, and check that configid= has the full key.
Docusign for Quickbase and EZ File Importer are listed in the portal, but their batch runs don't check batch configurations, so a mismatch never stops them. For Docusign batch runs, see Docusign batch email notification.
Learn more
Frequently asked questions
My run stopped with "The following parameters do not match the configuration" after I changed my formula. What do I do?
The new value isn't allowed yet. Open the configuration's Configured Parameters screen, select Modify on each listed parameter, and add the new value. If the new value is a mistake, fix the formula instead. See Change allowed values.
Where do I find the Config Key, and which configuration does my run use?
Open the extension's Configurations screen and compare the last 8 characters of the configid= value in your batch arguments with the Config Key column. Then give the configuration a Name so it's easy to find next time. See Find a configuration.
My batch run did nothing. Where's the error?
It depends on the extension; see Where you see a mismatch. PDF Stamper, Image Resizer/Rotator, and QB Maps geocoding runs write nothing to your app when the check fails, so check the configuration first.
My extension isn't on Batch Add-Ons. How do I create a configuration for it?
You can only add a configuration for an extension that's already listed. An extension is listed once it has a configuration, which the installation wizard usually creates. Image Resizer/Rotator's wizard doesn't create one yet. For an extension that isn't listed, submit a technical support case to have its first configuration created.
Do my batch runs need configid?
Yes. Every batch run of XL Docs, PDF Stamper, QB Maps, Exact Forms Plus, JuicedSign, PDF Merger, Package Builder, and Image Resizer/Rotator checks its batch configuration. Without configid= (or configkey=), the run stops with No ConfigID was passed in. This configuration requires a ConfigID.
Can I use configkey= instead of configid=?
Yes. Both take the Config Key. If the arguments include both, the extension uses configkey.
Where's the Config Key for my QB Courier or Text My QB notification?
Not in the Batch Configuration Portal. QB Courier and Text My QB keys belong to their own configurations, and you get them from their configurators. See Quickbase enhanced security email notifications.
If my run leaves out a parameter that's in the configuration, is it checked?
No. Only the parameters the run passes are checked. A configured parameter that isn't in the arguments doesn't stop the run.
Why are Docusign for Quickbase and EZ File Importer listed? Are their runs checked?
The installation wizard creates a batch configuration for them, so they're listed on Batch Add-Ons. Their batch runs don't check it.
A value with spaces or quotes looks right but doesn't match. Why?
Check upper and lower case and extra spaces. Double quotes around a value aren't part of it: a formula that sends fn="Invoice 2026" passes Invoice 2026, so enter the allowed value without the quotes. The easiest fix is to copy the value from the record's batch arguments field, or create the configuration with Paste Parameters, which removes the quotes for you.
How many allowed values can a parameter have?
Up to 10. Don't give one parameter values that differ only in upper and lower case, such as Invoice and invoice; change the formula so it always sends one spelling.
My new configuration created with Create Manually fails every run. Why?
Its parameters start with blank allowed values, which only allow an empty value. Set the values your run sends with Modify, or create the configuration with Paste Parameters instead.
How do I delete or disable a configuration, remove or rename a parameter, or get a new Config Key?
These can't be done in the portal. Submit a technical support case with the extension's name and the configuration's name or the last 8 characters of its key. Don't include the full key.
Who can see and change configurations?
Anyone who can open My Extensions in the Extensions Portal for your company. Treat a Config Key like a password.