Skip to main content

Troubleshooting

This guide helps you resolve common issues when using the Dime.Scheduler Zapier connector.

Authentication Issues​

API Key Not Accepted​

Symptoms:

  • "Invalid API key" error when testing connection
  • Authentication fails during Zap setup

Solutions:

  1. Verify the API key

    • Ensure there are no extra spaces when pasting
    • Check that the key hasn't been revoked or expired
    • Generate a new API key from Administration → API Keys if needed

  2. Confirm environment selection

    • Verify you're using an API key from the matching environment (Sandbox vs Production)
    • Disconnect and reconnect the Dime.Scheduler account in Zapier if needed

Environment Mismatch​

Symptoms:

  • Connection works but data doesn't appear
  • "Resource not found" errors

Solution:

Your API key is environment-specific. Ensure you selected the matching environment in Zapier (Sandbox vs Production). Disconnect and reconnect if you need to change environments.

Trigger Issues​

Trigger Not Firing​

Symptoms:

  • Zap doesn't run when appointments are created/updated/deleted
  • No new data appears in Zap history

Solutions:

  1. Check Zap status

    • Ensure the Zap is turned ON (not paused or draft)
    • Review error messages in the Zap history

  2. Re-register webhook

    • Webhooks are automatically created but may need to be refreshed
    • Toggle the Zap off and on to re-register the webhook

  3. Verify environment

    • Ensure appointments are being created in the same environment your Zap is monitoring

  4. Check filter criteria

    • Confirm appointments meet any filter criteria you've set in the Zap

Missing Data in Trigger Output​

Symptoms:

  • Trigger fires but some fields are empty or null
  • Expected data doesn't appear in subsequent steps

Solutions:

Some fields may be empty if they weren't populated in Dime.Scheduler:

  1. Check the source data

    • Verify the appointment in Dime.Scheduler has the fields populated
    • Some fields like resourceName require the appointment to have an assigned resource

  2. Use conditional logic

    • Add a Filter step in Zapier to only process appointments with required data
    • Handle empty fields gracefully in your Zap logic

  3. Map alternative fields

    • Use multiple identifier options (e.g., try appointmentGuid if appointmentId is empty)

Action Issues​

"Required Field Missing" Error​

Symptoms:

  • Action fails with "required field missing" message
  • Zap shows error in history

Solutions:

  1. Review required fields

    • Tasks: sourceApp, sourceType, jobNo, taskNo, and shortDescription are required
    • Resources: resourceNo is required
    • Appointments: Check the specific requirements for your item type

  2. Check data mapping

    • Ensure required fields are mapped to data from the trigger
    • Use the Zap history to identify which field is missing
    • Provide default values if trigger data might be missing

Duplicate Items Created​

Symptoms:

  • Multiple appointments/tasks/resources created when only one was expected
  • Data appears duplicated in Dime.Scheduler

Solutions:

  1. Prevent Zap loops

    • Bidirectional sync can create loops (Zap creates item → Trigger fires → Zap creates another item)
    • Add filters to skip items from specific source apps

  2. Use unique identifiers

    • Provide unique identifiers like appointmentNo, taskNo, or jobNo
    • The connector will update existing items if the identifier matches

  3. Add filter conditions

    • Use the sourceApp field to identify and skip items created by your Zap

"Item Not Found" Error​

Symptoms:

  • Set Attribute or Delete Item actions fail
  • Error says the appointment/task/resource doesn't exist

Solutions:

  1. Verify the item exists

    • Confirm the item is in Dime.Scheduler
    • Check you're using the correct environment (Sandbox vs Production)

  2. Check identifiers

    • Ensure you're using the correct identifier field and it's not empty
    • Try alternative identifiers (e.g., appointmentGuid instead of appointmentId)

  3. Add delay for timing issues

    • If creating then immediately updating an item, add a 1-2 second delay step
    • The item might not be fully indexed yet

Data Formatting Issues​

Date/Time Format Errors​

Symptoms:

  • "Invalid date format" error
  • Dates appear incorrect in Dime.Scheduler

Solution:

Dime.Scheduler expects ISO 8601 format: YYYY-MM-DDTHH:mm:ssZ (e.g., 2025-10-07T14:30:00Z). Use "Formatter by Zapier" to convert dates to ISO 8601 format in UTC timezone before sending to Dime.Scheduler.

Boolean Field Errors​

Symptoms:

  • Fields like locked, useFixedPlanningQuantity not working correctly
  • "Invalid boolean value" error

Solution:

Boolean fields expect true or false (lowercase), not "Yes/No" or "1/0". Use "Formatter by Zapier" to convert values if needed.

Number Field Errors​

Symptoms:

  • "Invalid integer" or "Invalid number" errors
  • Fields like importance not accepting values

Solution:

Ensure proper data types: integers require whole numbers (0, 1, 2), decimals allow fractional values (1.5, 2.75). Remove non-numeric characters using "Formatter by Zapier" if needed. Note that importance must be 0 (Low), 1 (Normal), or 2 (High).

Performance Issues​

Zap Running Slowly​

Symptoms:

  • Delays between trigger and action
  • Data takes a long time to sync

Solution:

Remove unnecessary steps and add filters early in the Zap to skip processing. Check Zapier's status page if issues persist - slow performance is often from other apps in your Zap.

Hitting Rate Limits​

Symptoms:

  • "Rate limit exceeded" errors
  • Actions fail during high-volume periods

Solution:

Use Zapier's "Delay" action to space out API calls or reduce the frequency of scheduled Zaps. If you consistently hit limits, contact Dime.Scheduler support to discuss increasing your rate limits.

Common Mistakes​

Using Wrong Item Type​

Ensure you understand the difference between item types:

  • Appointment: A scheduled time slot assigned to a resource (shows on the calendar)
  • Task: Work that needs to be done (may or may not be scheduled yet)
  • Job: A collection of tasks (like a project or work order)
  • Resource: A person, vehicle, or equipment that can be scheduled

Forgetting Source App and Source Type​

Always populate sourceApp and sourceType fields to track data lineage:

  • sourceApp: The name of the system (e.g., "Zapier", "Salesforce", "Google Sheets")
  • sourceType: The type of record (e.g., "FormSubmission", "Opportunity", "Booking")

This enables filtering and helps maintain data integrity.

Getting Help​

Debugging Tools​

Use Zap History to view detailed error messages and data from each step. Use Test Mode in the Zap editor to verify data flow between steps before enabling the Zap.

Still Stuck?​

If you're still experiencing issues:

  1. Check Zapier's Status Page

  2. Review Dime.Scheduler API Documentation

  3. Contact Support

    • Provide your Zap ID (found in Zap settings)
    • Include screenshots of error messages
    • Share the full error message from Zap History
    • Describe what you're trying to accomplish

  4. Zapier Community

Best Practices​

To avoid issues:

  • Test Zaps in Sandbox before deploying to Production
  • Use descriptive names for Zaps and custom fields
  • Monitor Zap History regularly for errors
  • Add filters early in the Zap to skip unnecessary processing
  • Always test after making changes to a Zap
Last updated on by Hendrik Bulens