Skip to content
Submit a Ticket Portal
  • There are no suggestions because the search field is empty.

How to Safely Reconnect the Ticketure Connector After a Salesforce Sandbox Refresh

Steps to check your sandbox connection, protect production data, and confirm the Ticketure Connector is working correctly after a refresh.

 Overview

A Salesforce sandbox refresh replaces existing sandbox data and configuration with a new copy from its source organization. For Full and Partial Copy sandboxes, that copy can include Ticketure Connector configuration that was originally designed for production.

If the connection is not reviewed after the refresh, sandbox activity could be sent to the wrong Ticketure environment or incoming synchronization could behave unexpectedly. This guide provides a safe post-refresh process.

Know your sandbox type

Sandbox type

What may be copied

Recommended approach

Full

Production data and configuration, including Custom Settings used by the Connector.

Treat the Connector as potentially production-connected until verified.

Partial Copy

Selected production data plus configuration, including Connector settings.

Treat the Connector as potentially production-connected until verified.

Developer / Developer Pro

Configuration is copied, but the complete Connector setup and supporting data may not be present.

Expect to verify or rebuild required sandbox configuration before testing.
Before the refresh
  • Record the scheduled refresh date and the Salesforce sandbox name.
  • Notify Ticketure Support or your Ticketure administrator before the refresh if the sandbox is actively connected.
  • Document the intended Ticketure target environment, seller, and integration user.
  • Pause planned Connector testing until the post-refresh review is complete.
  • Retain screenshots or notes for any sandbox-only settings that may need to be restored.
After the refresh
  1. Do not create carts, Contacts, Opportunities, or other Connector test records yet.
  2. Confirm that you are signed in to the refreshed Salesforce sandbox, not production.
  3. Open Ticketure Connector Settings and review the current connection and environment indicators.
  4. Confirm that the configured Ticketure system, seller, and endpoint belong to the intended Ticketure sandbox environment.
  5. Review the Salesforce authorization. Reconnect with the approved sandbox integration user if the authorization is missing, invalid, or belongs to the wrong user.
  6. Verify required Remote Site Settings, permissions, record types, Custom Settings, and other Connector configuration.
  7. Ask Ticketure Support to confirm or restore the Ticketure-side sandbox connection when required.

Stop if uncertain: If any setting appears to reference production, disable or leave the Connector inactive and contact Ticketure Support. Do not test the connection to see where the data goes.

Validation checklist

Complete these checks before allowing normal sandbox testing:

  • Salesforce organization is the intended refreshed sandbox.
  • Ticketure target is a non-production environment approved for testing.
  • The authorized Salesforce user is active and has the required Connector permissions.
  • Inbound Ticketure-to-Salesforce processing is configured for the sandbox.
  • Salesforce-to-Ticketure features are disabled unless they are intentionally being tested.
  • Remote Site Settings and endpoints reference the approved Ticketure environment.
  • No production credentials, URLs, carts, or customer records are being used for sandbox testing.
Run a controlled test
  1. Choose a clearly identified test customer and use only non-production data.
  2. Create one small test transaction using the workflow you need to validate.
  3. Confirm that the activity appears in the intended Ticketure sandbox and the refreshed Salesforce sandbox.
  4. Review the related Ticketure Event Queue records and confirm that they processed successfully.
  5. Verify the expected Contact, Opportunity, Opportunity Product, Payment, or Membership result.
  6. Test additional workflows only after the first transaction is confirmed end to end.
Common post-refresh symptoms

Symptom

What to review

OAuth or invalid_grant error

Reconnect the Salesforce authorization with an active, approved sandbox integration user.

No inbound events

Confirm the Ticketure-side sandbox connection, webhooks, authorization, and Salesforce endpoint.

Salesforce records do not push to Ticketure

Review Salesforce-to-Ticketure settings, supported record types, permissions, and Do Not Sync controls.

Unexpected production activity

Stop testing immediately, disable further Connector activity, document the affected records, and contact Ticketure Support.

Many Event Queue errors

Review one representative error before retrying. Correct the shared configuration problem first.
When to contact Ticketure Support

Contact Ticketure Support before testing if the correct target environment cannot be confirmed, Ticketure-side configuration must be restored, or the sandbox appears connected to production.

Include:

  • Organization name and Salesforce sandbox name
  • Sandbox type and refresh completion date
  • Intended Ticketure environment and seller
  • Screenshot of the relevant Connector settings with secrets removed
  • Any Event Queue record numbers and error messages
  • A description of what has already been tested