Skip to Content
IntegrationsAPNSandbox vs production

APN Sync — Sandbox vs Production

What Sandbox is

Sandbox is a test environment in AWS Partner Central. When FlowState is configured with Catalog = Sandbox, all CreateOpportunity, UpdateOpportunity, and related API calls include Catalog: "Sandbox" in the request payload. Opportunities created in Sandbox:

  • Are isolated from your real co-sell pipeline.
  • Do not count toward your partner tier metrics or AWS co-sell credit.
  • Do not trigger real engagement workflows with AWS.
  • Are visible only in the Sandbox section of Partner Central.

Sandbox is the default catalog when you first enable APN sync. FlowState displays a Sandbox mode banner in the APN sync section of the dashboard.

Testing safely

You can create a separate FlowState tenant for sandbox testing. Pair it with a HubSpot sandbox account and your AWS Partner Central Sandbox environment to test the full sync flow without affecting production data.

Validation checklist

Complete all of the following before flipping to Production:

  • At least 5 deals successfully complete the full sync sequence: not_synced → created → associated → submitted → in_review. Confirm each state transition in the FlowState APN sync view.
  • All sync error states have been exercised and resolved at least once: validation_error, conflict, integration_broken.
  • Conflict detection and resolution tested: update a conflict-detected field in both HubSpot and APN simultaneously; confirm FlowState detects the conflict; resolve it using resolve_apn_conflict; confirm sync resumes.
  • Inbound events tested: verify that a status change in Sandbox Partner Central (e.g., review status advancing to Action Required) is reflected in the HubSpot deal within 2 minutes.
  • Rate limiting tested: confirm that deals queued faster than 1 TPS process correctly without data loss (they are queued and retried automatically).
  • list_apn_sync_state() shows no deals in an error state.
  • list_apn_conflicts() returns zero open conflicts.

Moving to Production

Switching from Sandbox to Production requires completing a new APN integration setup. You must re-authorize FlowState in your Production AWS Partner Central account, which generates a new cross-account role and connection. Your existing Sandbox data and sync history will not carry over to Production.

Steps to connect Production

  1. Go to Settings → Integrations → APN → Disconnect to remove the Sandbox connection.
  2. Click Connect APN and follow the onboarding wizard to set up the Production connection using your Production AWS Partner Central account.
  3. In the wizard, select Production when prompted to choose a catalog.
  4. Verify the connection succeeds and confirm with Verify connection.

Deals that were synced in Sandbox mode remain as Sandbox opportunities in Partner Central. They are not migrated to Production. After connecting to Production, re-enable APN sync on deals that should be submitted to your Production co-sell pipeline.

Note: You cannot switch back from Production to Sandbox after connecting to Production without disconnecting and re-running the onboarding wizard.

Sandbox limitations

  • Sandbox Partner Central has the same API rate limits as Production (1 TPS, 10k/24h per partner account). Factor this into your testing if you are running bulk tests.
  • Not all Partner Central events are emitted in Sandbox. If inbound event testing is not working, check whether your AWS Partner Central Sandbox environment has EventBridge event publishing enabled.
  • apn_opportunity_id values from Sandbox are different from what Production would assign. Do not use Sandbox opportunity IDs in production workflows.
Field mappingConflicts & resolution