Common Issues

Connection issues

Authentication fails when entering API credentials

Coassemble requires two tokens: a User Token and an Organization Token. If either is missing or entered in the wrong field, the connection will fail. Double-check that you've copied both tokens from Coassemble's Settings → API section and pasted them into the correct fields in Coupler.io.

Tokens are case-sensitive and may contain special characters — copy-paste rather than retyping them manually.

Connection succeeds but no data appears in the destination

This usually means the connected Coassemble account has no data for the selected entity. For example, if you select Trackings but no learners have started any courses yet, the result will be an empty table. Try switching to the Courses entity to confirm the connection is working.

Missing data

Some courses are missing from the Courses entity

Only courses that are visible to the authenticated user's organization will be returned. If you have courses in a different organization or workspace, you'll need to create a separate data flow using that organization's token.

Tracking records are missing for some users

Trackings are only created when a learner actively starts a course. Users who have been assigned a course but haven't opened it yet won't appear in the Trackings entity. This is expected behavior — there's no record until the learner takes action.

completed_at field is empty for some tracking records

If a learner has started a course but not finished it, completed_at will be null. This is correct — only fully completed courses have a value in this field. Use the status and progress fields to identify in-progress learners.

Permission errors

"Unauthorized" or "403" error when connecting

This typically means the User Token belongs to an account that doesn't have API access enabled, or the Organization Token doesn't match the user's organization. Verify in Coassemble that API access is enabled for your account and that both tokens are from the same organization.

If your Coassemble plan doesn't include API access, you won't be able to connect via Coupler.io. Check with your Coassemble account administrator or plan details.

Data discrepancies

Progress percentages don't match what I see in Coassemble

Coupler.io pulls a snapshot of data at the time of the sync. If a learner completed more of a course after your last data flow run, the progress field in your destination will be out of date. Run the data flow again or increase your refresh frequency to keep the data current.

Rate limits

Data flow fails or times out with large tracking datasets

Coassemble's API may throttle requests when pulling large volumes of tracking data. If this happens, try syncing individual entities in separate data flows rather than combining multiple sources in a single run. Splitting the load can help avoid timeout errors.