Skip to main content

Jobber Error Messages

Every error code the iPaaS.com Jobber integration can record, grouped by flow, with the exact message, what causes it and how to resolve it.

Overview

This article lists the error messages the Jobber integration can record in iPaaS.com, grouped by flow. Each error carries a stable code you can search for on this page, followed by the exact message, the condition that causes it, and how to resolve it. Errors appear in iPaaS.com under Dashboard / Integration Monitoring / Error Logs. In each message, words in braces, such as {action} or {name}, stand for the details of the record or step that failed.

iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.

Messages that say "click Authorize" refer to the subscription's Authenticate action (the lock icon on its Subscription Settings page).

Some resolutions refer to your Managed Integration Service Provider (MiSP): the partner who set up and manages your iPaaS.com integration, including its mappings, filters, settings and Jobber authorization.

Supported Flows

  • Authentication and Connection

  • Webhooks

  • All Flows

  • Add/Update Jobber Client TO iPaaS.com

  • Add/Update Jobber Invoice TO iPaaS.com

  • All Flows FROM iPaaS.com

  • Add/Update Jobber Client FROM iPaaS.com

  • Add/Update Jobber Product or Service FROM iPaaS.com

  • Add/Update Jobber Request FROM iPaaS.com

Error Collection

Authentication and Connection

Jobber app credentials not configured

JOBR-AUTH-1001 - The Jobber app's {ClientId/ClientSecret} is not configured on this integration version. This is set by iPaaS.com, not by the subscriber: contact iPaaS.com support.

  • Description: The Jobber app's client id or client secret is empty on the version of the integration your subscription uses. iPaaS.com sets these values for every subscriber; when they are missing, every subscription on that version shows this error.

  • Resolution: You cannot fix this from your subscription. Contact iPaaS.com Support at support@ipaas.com and include the error's reference from Error Logs, so iPaaS.com can set the integration's Jobber app credentials.

Subscription not authorized

JOBR-AUTH-1002 - This subscription is not connected to Jobber yet. Open the subscription and click Authorize.

  • Description: The subscription has no saved Jobber sign-in, because Authenticate was never completed.

  • Resolution: Open the subscription in iPaaS.com, click Authenticate, sign in to Jobber with an admin login for the account, and click Allow Access. Then resend the record.

Authorization no longer accepted

JOBR-AUTH-1003 - Jobber no longer accepts this subscription's authorization (it was disconnected, re-authorized elsewhere, or the app changed). Open the subscription and click Authorize again.

  • Description: Jobber refused the subscription's saved sign-in twice within 10 minutes. This happens when the iPaaS.com app was disconnected in Jobber, the app was authorized again elsewhere for the same Jobber account, or the app's credentials changed.

  • Resolution: Click Authenticate on the subscription again, then resend the record. If it keeps happening, check that iPaaS.com is still connected to your Jobber account (in Jobber's settings for connected apps), and that the same Jobber account was not authorized on a second iPaaS.com subscription: connect each Jobber account to only one subscription.

Token endpoint error

JOBR-AUTH-1005 - Jobber's token endpoint answered HTTP {status}: {text}

  • Description: Jobber's sign-in service failed, or answered something unreadable, while the integration renewed the subscription's sign-in. It can also appear briefly when several transfers renew the sign-in at the same moment.

  • Resolution: Usually temporary: iPaaS.com retries the transfer. If it persists, check Jobber's status page at status.getjobber.com, then click Authenticate on the subscription again.

No Jobber account returned

JOBR-AUTH-1006 - Jobber returned no account for this authorization. Click Authorize again.

  • Description: When iPaaS.com checked the subscription's connection, Jobber returned no account for the saved sign-in.

  • Resolution: Click Authenticate again and sign in to Jobber with an admin login for the business account.

App credentials rejected

JOBR-AUTH-1007 - Jobber did not recognize the integration's app credentials. Contact iPaaS.com support.

  • Description: Jobber's sign-in service did not recognize the client id and secret of the integration's Jobber app. These are set by iPaaS.com, not in your subscription.

  • Resolution: You cannot fix this from your subscription. Contact iPaaS.com Support at support@ipaas.com and include the error's reference from Error Logs, so iPaaS.com can update the integration's Jobber app credentials.

Access not granted

JOBR-AUTH-1008 - Jobber did not grant access ({error}). Click Authorize again and choose Allow Access.

  • Description: On Jobber's consent page, the person authorizing declined, or Jobber reported an error instead of granting access. The text in parentheses is Jobber's reason.

  • Resolution: Click Authenticate again, sign in with an admin login for the Jobber account, and choose Allow Access. If Jobber shows an error instead of Allow Access, note its exact words and give them to your MiSP.

No authorization code

JOBR-AUTH-1009 - Jobber's sign-in returned no authorization code. Click Authorize again.

  • Description: Jobber's sign-in returned to iPaaS.com without the authorization code the integration needs to finish connecting.

  • Resolution: Click Authenticate again and finish Jobber's sign-in in the same browser window.

Authorization code refused

JOBR-AUTH-1010 - Jobber refused the authorization code (HTTP {status}: {text}). Click Authorize again; codes expire after 10 minutes.

  • Description: Jobber refused to exchange the authorization code for a sign-in: the code expired after 10 minutes, was already used, or the sign-in was started from a different address.

  • Resolution: Click Authenticate again and complete Jobber's sign-in within 10 minutes.

Saved sign-in refused once (retrying)

JOBR-AUTH-1011 - Jobber refused this subscription's saved sign-in once; it is usually renewed by another transfer at the same moment. Retrying in 30 seconds. If it is refused again within 10 minutes, the error becomes JOBR-AUTH-1003 (Authorize again).

  • Description: Jobber refused the saved sign-in once, usually because another transfer renewed it at the same moment. The integration asks iPaaS.com to retry the transfer 30 seconds later. iPaaS.com holds the transfer as delayed ("Exceeded Rate Limit - Hook Delayed") and retries it, so this message itself may not appear in Error Logs. If Jobber refuses the sign-in again within 10 minutes, the transfer stops with JOBR-AUTH-1003.

  • Resolution: No action: the transfer is retried. If JOBR-AUTH-1003 follows, click Authenticate on the subscription.

API Url setting not usable

JOBR-VALD-1015 - The subscription's API Url setting is not usable: {reason}. Set it back to https://api.getjobber.com/api/graphql in the subscription settings, or contact iPaaS.com support.

  • Description: The API Url setting is not an https address on Jobber's own domain, so the integration refuses to send the subscription's Jobber access there. The {reason} says what is wrong, for example "it must start with https://". While the setting is wrong, every transfer shows only "Unable to connect to subscription", and this coded message is in the iPaaS.com Logs entry with the same time and reference id.

  • Resolution: Open the subscription's settings, set API Url back to https://api.getjobber.com/api/graphql, and click Apply. Then resend the records that failed.

Webhooks

No webhook endpoint returned

JOBR-EXTN-1004 - Jobber did not return a webhook endpoint for {topic}.

  • Description: When a webhook scope was turned on, Jobber accepted the registration but returned no notification endpoint, so the integration could not save it. The {topic} names the scope, for example CLIENT_CREATE.

  • Resolution: Turn the scope off and on again. If it persists, use the matching poll scope instead (CLIENT_POLL, INVOICE_POLL or PRODUCT_OR_SERVICE_POLL).

Jobber can also refuse a webhook scope being turned on or off. That error is JOBR-VALD-1001, and its message names the scope, for example "while registering Jobber's CLIENT_CREATE notifications". See Jobber did not accept the record under All Flows FROM iPaaS.com.

All Flows

Jobber refused the token

JOBR-AUTH-1004 - Jobber refused the authorization while {action}. Open the subscription and click Authorize again.

  • Description: Jobber answered that the request was not authorized, even after the integration renewed the subscription's sign-in once.

  • Resolution: Click Authenticate on the subscription again, then resend the record.

Jobber rejected the request

JOBR-EXTN-1001 - Jobber rejected the request while {action}: {messages}

JOBR-EXTN-1001 - Jobber returned no result while {action}.

  • Description: Jobber rejected the request and returned its own message, for example a field or value it does not accept, or a record id it cannot read. The second message appears when Jobber answers a create or update with no result.

  • Resolution: Read Jobber's message in the error. It usually names the field or value Jobber did not accept: correct the mapping or the record, then resend. If the error came from a Manual Sync, check the record id you entered. If the message names nothing you can change, give the error to your MiSP.

Jobber unreachable or unreadable reply

JOBR-EXTN-1002 - Could not reach Jobber while {action}: {details}

JOBR-EXTN-1002 - Jobber returned HTTP {status} with no readable body while {action}.

JOBR-EXTN-1002 - Jobber returned HTTP {status} while {action}: {messages}

JOBR-EXTN-1002 - Jobber returned HTTP {status} while {action}.

  • Description: Jobber could not be reached, answered with a server error (HTTP 500 or above), or sent a reply the integration could not read.

  • Resolution: Usually temporary: iPaaS.com retries the transfer. If it persists, check Jobber's status page at status.getjobber.com. If Jobber reports no problem and the error continues, give the error to your MiSP.

Jobber rate limit

JOBR-EXTN-1003 - Jobber request limit reached while {action}: retry after {n}s.

JOBR-EXTN-1003 - Jobber query cost limit reached while {action}: retry after {n}s.

  • Description: Jobber's request limit (too many requests) or query cost limit was reached. iPaaS.com holds the transfer and retries it after the reset time Jobber gives, so the transfer can show as delayed rather than as an error.

  • Resolution: No action: iPaaS.com retries automatically after the limit resets.

Delete not supported

JOBR-VALD-1004 - Deleting clients in Jobber is not supported by this integration.

JOBR-VALD-1004 - Deleting products or services in Jobber is not supported by this integration; to hide one in Jobber, set the iPaaS.com product's status to Disabled or Discontinued.

JOBR-VALD-1004 - Deleting invoices or work requests in Jobber is not supported by this integration.

  • Description: A delete was sent to the integration, for example by a mapping collection set up to delete records. This integration never deletes records in Jobber.

  • Resolution: Archive the client, void the invoice or archive the work request in Jobber by hand. For a product or service, set the iPaaS.com product's status to Disabled or Discontinued, and the integration hides the item in Jobber. If a collection was set up to send deletes to Jobber, change it back to Add/Update or remove it.

Record moves with its parent

JOBR-VALD-1017 - This record moves with its transaction; transfer the transaction, and remove any collection that sends this record type on its own.

JOBR-VALD-1017 - This record moves with its transaction; poll the transaction.

JOBR-VALD-1017 - A client address moves with its client; transfer the client, and remove any collection that sends addresses on their own.

JOBR-VALD-1017 - A client address moves with its client; poll the client.

  • Description: A child record (an invoice line, payment, tax, discount or address, or a client's billing address) was sent on its own instead of with its invoice or client. This usually comes from a Manual Sync or resend of the child record, or from a collection added to send those records alone.

  • Resolution: Resend the parent invoice or client instead; its lines, payments, taxes, discounts and addresses go with it. Remove a collection only if it was added to send those records alone. Never remove the default child collections that come with the templates (Add/Update Jobber Invoice Line TO iPaaS.com, Add/Update Jobber Invoice Payment TO iPaaS.com, Add/Update Jobber Invoice Tax TO iPaaS.com, Add/Update Jobber Invoice Address TO iPaaS.com, Add/Update Jobber Invoice Discount TO iPaaS.com, Add/Update Jobber Client Billing Address TO iPaaS.com, Add/Update Jobber Client Billing Address FROM iPaaS.com and Add/Update Jobber Request Line FROM iPaaS.com): they carry those records with their parent.

Data type or direction not supported

JOBR-VALD-1018 - This data type or direction is not supported by the Jobber integration; remove that mapping collection. (Call to {operation} with unhandled parameters: ...)

  • Description: A mapping collection asks the integration for a data type or direction it does not have, for example a gift card collection. The Jobber integration supports clients and products or services in both directions, invoices TO iPaaS.com, and work requests FROM iPaaS.com.

  • Resolution: Remove the mapping collection that was added for the unsupported data type or direction. If the collection is one of the default Jobber collections, do not remove it: give the error's reference to your MiSP, who can raise it with iPaaS.com Support.

iPaaS.com API call failed

JOBR-IPAS-1001 - iPaaS.com's API failed while {action} (HTTP {status}): {message}

  • Description: A call from the integration to iPaaS.com failed or was refused, for example while looking up a record's link, reading the integration's settings, or sending a related record first.

  • Resolution: Usually temporary: iPaaS.com retries the transfer. If it persists, or the status is 401 or 403, give the error's reference to your MiSP, who can raise it with iPaaS.com Support. If every subscription on the integration shows it at once, contact iPaaS.com Support at support@ipaas.com, as for JOBR-AUTH-1001.

Add/Update Jobber Client TO iPaaS.com

Client has no email address

JOBR-VALD-1016 - Jobber client {name} (clients/{number}) has no email address, and iPaaS.com customers need one. Add an email to the client in Jobber; its next change sends it, or run a Manual Sync for the client.

JOBR-VALD-1016 - Jobber invoice {number}'s client {name} (clients/{number}) has no email address, and iPaaS.com customers need one. Add an email to the client in Jobber, then resend the invoice.

  • Description: iPaaS.com customers need an email address, and the Jobber client, or the client of an invoice being sent, has none. The {number} after clients/ is the number at the end of the client's Jobber web address. A prospect (a lead with no invoice) is skipped by the default filter instead. This check runs before the collection's filter, so changing the filter does not silence it.

  • Resolution: Add an email address to the client in Jobber. The client's next change sends it, or run a Manual Sync of the client. A retry without the email fails the same way, so after adding the email, resend each invoice that stopped with this error.

Add/Update Jobber Invoice TO iPaaS.com

An invoice whose client has no email address stops with JOBR-VALD-1016 (see Add/Update Jobber Client TO iPaaS.com).

Invoice over 100 lines

JOBR-VALD-1009 - Jobber invoice {number} has more than 100 line items; this integration sends invoices of up to 100 lines.

  • Description: The Jobber invoice has more than 100 line items. Voiding the invoice in Jobber does not clear this error; it repeats until iPaaS.com stops retrying.

  • Resolution: Enter that invoice in the receiving system by hand. If your invoices often exceed 100 lines, tell your MiSP.

Invoice line has no iPaaS.com SKU

JOBR-VALD-1013 - Invoice line "{name}" is a one-off line and the subscription's Fallback Line SKU setting is empty. Enter the SKU of the iPaaS.com product used for one-off lines in the subscription settings, then resend the invoice.

JOBR-VALD-1013 - Invoice line "{name}" uses a Jobber item that is not in iPaaS.com, and the subscription's Fallback Line SKU setting is empty. Send the item TO iPaaS.com (check the Product TO collection and its filter, or run a Manual Sync of the item) or enter a Fallback Line SKU, then resend the invoice.

  • Description: The first message: an invoice line was typed on the invoice with no Jobber item (a one-off line), and the subscription's Fallback Line SKU setting is empty. The second message: the line's Jobber item is not in iPaaS.com and the setting is empty, because Add/Update Jobber Product or Service TO iPaaS.com is off, its filter left the item out, the item was hidden in Jobber before it was ever sent, or the item's own transfer failed.

  • Resolution: For a one-off line, create (or pick) an iPaaS.com product for one-off lines, enter its SKU in the subscription's Fallback Line SKU setting, click Apply, and resend the invoice. The SKU must belong to a product that exists in iPaaS.com, or iPaaS.com refuses the invoice. For an item line, make Add/Update Jobber Product or Service TO iPaaS.com send the item: check that the collection is on and its filter accepts the item; if the item is hidden in Jobber and was never sent, show it in Jobber with the product webhook scopes on, which sends it; if the item's own transfer failed, fix that error. Or set Fallback Line SKU. Then resend the invoice.

Invoice over 50 payments

JOBR-VALD-1014 - Jobber invoice {number} has more than 50 payments; this integration sends invoices with up to 50 payments.

  • Description: The Jobber invoice has more than 50 payment records. Jobber's bookkeeping entries (a void, a bad-debt write-off, a correction) count toward the 50, although they are not sent as payments.

  • Resolution: Enter that invoice and its payments in the receiving system by hand. If your invoices often exceed 50 payments, tell your MiSP.

Linked item's SKU unreadable

JOBR-EXTN-1005 - Could not read the SKU of iPaaS.com product {id} for invoice line "{name}": {details}

JOBR-EXTN-1005 - iPaaS.com product {id} for invoice line "{name}" has no SKU.

  • Description: An invoice line's Jobber item is linked to an iPaaS.com product, but the product's SKU could not be read at that moment, or the product has no SKU. The integration stops rather than send a linked item's line under the fallback SKU.

  • Resolution: If the SKU could not be read, this is usually temporary and the invoice is retried; if it persists, check that the iPaaS.com product named in the error still exists, then resend the invoice. If the product has no SKU, give the iPaaS.com product named in the error a SKU, then resend the invoice.

All Flows FROM iPaaS.com

Jobber did not accept the record

JOBR-VALD-1001 - Jobber did not accept the record while {action}: {messages}

  • Description: Jobber refused a create or update and named the field or value, for example an invalid email address. The usual case on Add/Update Jobber Product or Service FROM iPaaS.com is "A product or service already exists with that name": Jobber keeps item names unique, hidden items included, and the integration's name search does not find hidden items, so it cannot link one. The same refusal appears when two Product or Service FROM collections both accept the same product. This code is also used when Jobber refuses a webhook scope being turned on or off. "Should only have one hook of that topic per account per url" means Jobber already has notifications registered for that event from an earlier activation; turning several scopes on at the same moment can leave such a registration behind. "Could not delete webhook" means Jobber could not remove the registration when the scope was turned off.

  • Resolution: Correct the value Jobber names in the source record or the mapping, then resend. For "already exists with that name", set the Collision Handling Method on Add/Update Jobber Product or Service FROM iPaaS.com (under Mappings) to Update and Link, show the hidden item in Jobber or rename one of them, then resend. If the message says it happened while hiding the new product or service, the item was created in Jobber: resend the product with Update and Link set, and it is linked. If two collections of the same type both accept the product, change their filters so they have no record in common. For a webhook scope, turn scopes on one at a time. An earlier registration cannot be removed from iPaaS.com and keeps delivering that event's notifications: give the scope name and the time of the error to your MiSP, who can raise it with iPaaS.com Support.

No Jobber id to update

JOBR-VALD-1002 - The customer has no Jobber id to update.

JOBR-VALD-1002 - The product has no Jobber id to update.

JOBR-VALD-1002 - The order has no Jobber work request id to update.

  • Description: An update arrived for a customer, product or order that is not linked to a Jobber record.

  • Resolution: Resend the record so it is created in Jobber, or link it to its Jobber record, then resend.

Add/Update Jobber Client FROM iPaaS.com

Jobber client no longer exists

JOBR-VALD-1003 - Jobber client {id} no longer exists. Remove the customer's Jobber link in iPaaS.com to create it again.

JOBR-VALD-1003 - Jobber client {id} no longer exists. Remove the customer's Jobber link in iPaaS.com and send the order again.

  • Description: The Jobber client the customer is linked to was deleted in Jobber (an archived client still exists and does not cause this). The second message appears on Add/Update Jobber Request FROM iPaaS.com, when an order's customer is linked to the deleted client.

  • Resolution: Remove the customer's Jobber link in iPaaS.com, then resend the customer, or the order: an order sends its customer to Jobber again first.

Several Jobber clients share the email

JOBR-VALD-1005 - {n} Jobber clients share the email {email}; merge them in Jobber, or link the customer by hand.

  • Description: This collection's Collision Handling Method is set to a method other than Error, so before creating a client the integration searches Jobber for a client with the customer's email address (email is the only field it matches on). Jobber allows several clients with one email, and the search found more than one, so the integration cannot choose which to link.

  • Resolution: Merge the duplicate clients in Jobber, or link the customer to one of them by hand, then resend the customer.

Client needs a name

JOBR-VALD-1006 - Jobber needs a first name, last name or company name to create a client.

  • Description: The customer reached Jobber with no first name, last name or company name, for example because those mappings were removed or return nothing. The default filter sends only customers with a first and last name, or a company.

  • Resolution: Give the customer a name or a company in the source system, or map one, then resend the customer.

Add/Update Jobber Product or Service FROM iPaaS.com

Item needs a name

JOBR-VALD-1007 - Jobber needs a name to create a product or service.

  • Description: The product reached Jobber with no name, for example because the Name mapping was removed or returns nothing.

  • Resolution: Map the product's name (or description) to Name, then resend the product.

Several Jobber items share the name

JOBR-VALD-1008 - {n} Jobber items are named "{name}"; rename one in Jobber, or link the product by hand.

  • Description: This collection's Collision Handling Method is set to a method other than Error, so before creating an item the integration looks for a shown Jobber item with the product's name (letter case ignored; name is the only field it matches on). It found more than one, so it cannot choose which to link. Jobber normally keeps item names unique, so this is rare.

  • Resolution: Rename the duplicate items in Jobber, or link the product to one of them by hand, then resend the product.

Add/Update Jobber Request FROM iPaaS.com

An order whose customer is linked to a Jobber client that was deleted stops with JOBR-VALD-1003 (see Add/Update Jobber Client FROM iPaaS.com).

Order's customer not in Jobber

JOBR-VALD-1011 - The order's customer is not in Jobber yet, so the work request can't be created. The integration sends the customer first; if this persists, check that the Customer FROM iPaaS.com filter accepts the customer, and the customer's own transfer for an error.

  • Description: The order's customer is not in Jobber, so the work request cannot be created. The integration sends the customer first; the customer's own transfer was skipped, most often by the filter of Add/Update Jobber Client FROM iPaaS.com, or it failed. iPaaS.com retries the order, and it keeps failing until the customer reaches Jobber.

  • Resolution: Check that Add/Update Jobber Client FROM iPaaS.com is on and that its filter accepts the customer (a first and last name, or a company). Check the customer's own transfer for its error and fix it, then resend the order.

Request created without its note

JOBR-VALD-1010 - The work request was created in Jobber, but its note was not added: {reason}

  • Description: The work request was created in Jobber and linked to the order, but adding the order's note to it failed. The {reason} is Jobber's or the integration's message for the failed note.

  • Resolution: No resend is needed: the work request exists and is linked. Add the note in Jobber by hand if your team needs it.

Related Documents

Did this answer your question?