Task not created

[arslan-icomm]

Silent failure when using taskTemplateId with quickConnectId for self-assign scenarios
Environment

• amazon-connect-taskjs version: 2.0.0

Issue Description
The library silently fails when creating tasks with both taskTemplateId and quickConnectId parameters for self-assignment scenarios.

Steps to Reproduce:
1. Create a task template with:
2. Assign-to field set as default
3. Self-assign option enabled
4. Use the library to create a task with payload: { name: 'Test Task', taskTemplateId: 'template-id', quickConnectId: 'agent-quick-connect-id', references: {}
5. Task creation fails silently (no error thrown)
Expected Behavior

• Task should be created successfully, OR
• Clear error message should be returned explaining parameter conflict

Actual Behavior

• Silent failure - no task created
• No error message in success/failure callbacks
• Only works when quickConnectId is excluded

Workaround
Currently excluding quickConnectId for self-assign scenarios:

{
name: 'Test Task',
taskTemplateId: 'template-id',
references: {
}
}

Root Cause
Appears to be a race condition or parameter validation conflict between taskTemplateId and quickConnectId when both are present.
Request

• Fix silent failure - return proper error messages
• Clarify parameter compatibility in documentation
• Support both parameters when appropriate for self-assign scenarios