Common Issues

Connection issues

API key is invalid or expired

If you see "Authentication failed" or "Invalid API key" when testing the connection, your API key may be incorrect or no longer active.

Fix: Go to your TimeTonic account settings, regenerate your API key, and paste the new key into Coupler.io. Test the connection again.

Cannot see my workspace in the dropdown

If the workspace dropdown is empty or doesn't show the workspace you expect, your API key may not have access to it.

Fix: Verify that your TimeTonic user account has permission to access the workspace. Ask your TimeTonic admin to confirm your role or add you to the workspace. Then regenerate your API key and test the connection again.

"No tables found" message

If after selecting a workspace, no tables appear in the table dropdown, the workspace may be empty or your permissions are limited.

Fix: Check with your TimeTonic admin to confirm that tables exist in the selected workspace. Verify that your user account has permission to view those tables. If you just created the workspace, you may need to create a table first before the connector can access it.

Missing data

Exported data shows fewer rows or columns than expected

If your export is missing rows or columns, you may have selected a view that filters or limits the data.

Fix: Check the view you selected. Try switching to the "All" view or default view to see if more data appears. You can also check your TimeTonic table settings to confirm that views are not hiding columns.

Recent hours or entries are not showing up

If you logged hours in TimeTonic but they don't appear in your Coupler.io export, the data may still be in draft or pending status.

Fix: In TimeTonic, check the status of your time entries (draft, submitted, approved). Export views or reports that include the status filter you need. If entries are still in draft, submit or approve them in TimeTonic first, then re-run the data flow.

Employee names or project names appear as IDs instead of names

If your export shows ID codes instead of human-readable names, the view may be configured to show IDs.

Fix: In your TimeTonic table settings, check if the view displays ID columns or name columns. You may need to adjust the view columns or create a Join in Coupler.io to look up names from a reference table (e.g., employee or project master data).

Permission errors

"Permission denied" when accessing a workspace or table

Your API key or user account does not have permission to access the selected workspace or table.

Fix: Ask your TimeTonic admin to grant you access to the workspace and table you're trying to export. Ensure your user role includes read access. After permissions are updated, regenerate your API key and re-test the connection.

Can connect but cannot see certain tables

You have access to the workspace but not all tables are visible in the dropdown.

Fix: Check your TimeTonic user role. Some users have limited access to certain tables or modules (e.g., reports, projects). Ask your admin to verify which tables your role can access.

Data discrepancies

Hours totals don't match TimeTonic UI

The sum of hours in your Coupler.io export may differ from what you see in the TimeTonic interface.

Fix: Check if the exported view includes filters (e.g., approved entries only, specific date range, or billable entries only). Compare the view's filter settings in TimeTonic to your export. If you need all hours including drafts, switch to an unfiltered view.

Date or time values are off by a few hours

TimeTonic stores times in UTC, but your workspace may be configured for a different time zone.

Fix: Check your TimeTonic workspace time zone settings. If needed, add a calculated column in your destination (Google Sheets or BigQuery) to convert times to your local zone. You can also check the time zone of the device where times were logged.

Rate limits

Data flow runs are slow or timing out

If your TimeTonic export takes a long time or fails, you may be hitting API rate limits or exporting too much data at once.

Fix: Try exporting a smaller date range or use a filtered view to reduce the number of rows. For large exports, consider splitting into multiple data flows (e.g., one per month or per project). Schedule exports during off-peak hours to avoid competing with other users.