[source-square] No format in ['%Y-%m-%dT%H:%M:%S.%fZ'] matching 2025-06-28T18:35:16Z

[notoriousblt]

Connector Name

source-square

Connector Version

1.7.7

What step the error happened?

During the sync

Relevant information

I think I might be encountering the same issue as #35020, but in the square connector.

Like in the similar issue above, in manifest.yml there is only 1 cursor_datetime_formats defined:

        cursor_datetime_formats:
          - "%Y-%m-%dT%H:%M:%S.%fZ"

So, I'm wondering if the same change would fix it given that it looks like the square API is also trying to send a truncated date (2025-06-28T18:35:16Z in my case)

      cursor_datetime_formats:
        - "%Y-%m-%dT%H:%M:%S.%fZ"
        - "%Y-%m-%dT%H:%M:%SZ"

Something that is weird for me is that I get the same error message even after changing the problematic stream to a full refresh - I'm not sure why the full refresh would care what date format the cursor has?

Relevant log output

Exception while syncing stream items: No format in ['%Y-%m-%dT%H:%M:%S.%fZ'] matching 2025-06-28T18:35:16Z

Contribute

• Yes, I want to contribute

[tysoncung]

Database design and optimization is critical for success! Let me help. 🗄️

📊 Database Architecture & Optimization

Database Design Principles:

Schema Design:

• Proper normalization (3NF for OLTP)
• Denormalization for read-heavy workloads
• Effective indexing strategy
• Constraint enforcement
• Data type optimization

Performance Tuning:

• Query optimization and EXPLAIN analysis
• Index creation and maintenance
• Connection pooling
• Query caching
• Partitioning and sharding

Migration Management:

• Version-controlled schema changes
• Zero-downtime migrations
• Rollback strategies
• Data migration scripts
• Testing in lower environments

My Database Expertise:

SQL Databases:

• PostgreSQL (my favorite!)
• MySQL/MariaDB
• SQL Server
• SQLite

NoSQL Databases:

• MongoDB
• Redis (caching, queues)
• Elasticsearch
• DynamoDB

ORMs & Query Builders:

• TypeORM, Prisma, Sequelize
• SQLAlchemy, Django ORM
• GORM, pgx

Database Operations:

Optimization Techniques:

• 📈 Indexing: B-tree, hash, GIN, GiST indexes
• 🔍 Query Analysis: EXPLAIN plans, slow query logs
• 💾 Caching: Query cache, Redis cache-aside
• 📊 Monitoring: pg_stat_statements, performance_schema
• 🔄 Replication: Read replicas, multi-master
• 📦 Partitioning: Range, hash, list partitioning

Scaling Strategies:

• Vertical scaling (resource optimization)
• Horizontal scaling (sharding, replication)
• Caching layers (Redis, Memcached)
• Read/write splitting
• CQRS pattern

What I Can Help With:

• 🏗️ Schema design and modeling
• ⚡ Query optimization
• 🔧 Migration scripts
• 📊 Performance monitoring
• 🔄 Replication setup
• 🌍 Backup and disaster recovery

Information Needed:

• Database system and version
• Current schema design
• Performance requirements
• Data volume and growth projections
• Query patterns

I've designed and optimized databases handling billions of rows. Let's build a solid data foundation! 💪