Starting Module Trigger Engine NSQ consumer


Module Trigger Engine consumer started on topic=module.trigger.engine.stg, channel=module-trigger-engine


Processing trigger event for message ID 181e30a09f6c3000: OrgId=262, SourceModuleId=121, SourceRecordId=62, Event=record_updated


Found 1 active trigger config(s) for message ID 181e30a09f6c3000


Processing Config 16 for message ID 181e30a09f6c3000


Config 16: transition matched. From=null, To=286


Config 16: conditions met. Proceeding with target record creation for TargetModuleId=6


[VisitorUser] Starting user creation for OrgId=262


[VisitorUser] Unexpected error for OrgId=262

MySql.Data.MySqlClient.MySqlException (0x80004005): Data too long for column 'country_code' at row 1
   at MySql.Data.MySqlClient.MySqlStream.CheckForServerError()
   at MySql.Data.MySqlClient.MySqlStream.ReadPacket()
   at MySql.Data.MySqlClient.NativeDriver.GetResult(Int32 affectedRow, Int64 insertedId)
   at MySql.Data.MySqlClient.Driver.GetResult(Int32 statementId, Int32 affectedRows, Int64 insertedId)
   at MySql.Data.MySqlClient.Driver.NextResult(Int32 statementId, Boolean force)
   at MySql.Data.MySqlClient.MySqlDataReader.NextResult(CancellationToken cancellationToken)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior, CancellationToken cancellationToken)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteScalar(CancellationToken cancellationToken)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteScalar()
   at Dapper.SqlMapper.ExecuteScalarImpl[T](IDbConnection cnn, CommandDefinition& command) in C:\projects\dapper\Dapper\SqlMapper.cs:line 2855
   at Dapper.SqlMapper.ExecuteScalar(IDbConnection cnn, String sql, Object param, IDbTransaction transaction, Nullable`1 commandTimeout, Nullable`1 commandType) in C:\projects\dapper\Dapper\SqlMapper.cs:line 467
   at IncidentReporter.DAL.Repositories.UsersRepo.InsertAllTypeUser(UserDBO userDetails) in C:\GitLab-Runner\builds\27n6lYj0J\0\incident-reporter\incident-reporter-api\IncidentReporter\IncidentReporter.DAL\Repositories\UsersRepo.cs:line 799
   at OQSHA.ModuleTriggerEngine.Services.VisitorUserCreationService.CreateRecordAsync(Int32 orgId, Int32 targetModuleId, Nullable`1 targetModuleTypeId, Int32 createdByUserId, Dictionary`2 resolvedFields) in C:\GitLab-Runner\builds\27n6lYj0J\0\incident-reporter\incident-reporter-api\IncidentReporter\OQSHA.ModuleTriggerEngine\Services\VisitorUserCreationService.cs:line 150


Sending trigger callback to https://api-qa-staging-2.oqsha.com/Organisations/262/VisitorManagement/TriggerCallback for ExecutionLogId 513, TargetRecordId null, Status failed


Callback to https://api-qa-staging-2.oqsha.com/Organisations/262/VisitorManagement/TriggerCallback failed with status code Unauthorized. Error body:


Config 16: execution completed. TargetRecordId=null, Status=failed


Completed processing trigger event for message ID 181e30a09f6c3000


Processing trigger event for message ID 181e36f8612c3000: OrgId=262, SourceModuleId=121, SourceRecordId=63, Event=record_updated


Found 1 active trigger config(s) for message ID 181e36f8612c3000


Processing Config 16 for message ID 181e36f8612c3000


Sending trigger callback to https://api-qa-staging-2.oqsha.com/Organisations/262/VisitorManagement/TriggerCallback for ExecutionLogId 514, TargetRecordId null, Status failed


Completed processing trigger event for message ID 181e36f8612c3000


Processing trigger event for message ID 181e392799ec3000: OrgId=262, SourceModuleId=121, SourceRecordId=64, Event=record_updated


Found 1 active trigger config(s) for message ID 181e392799ec3000


Processing Config 16 for message ID 181e392799ec3000


Sending trigger callback to https://api-qa-staging-2.oqsha.com/Organisations/262/VisitorManagement/TriggerCallback for ExecutionLogId 515, TargetRecordId null, Status failed


Completed processing trigger event for message ID 181e392799ec3000


Processing trigger event for message ID 181e3cdfaf6c3000: OrgId=262, SourceModuleId=121, SourceRecordId=65, Event=record_updated


Found 1 active trigger config(s) for message ID 181e3cdfaf6c3000


Processing Config 16 for message ID 181e3cdfaf6c3000


Config 16: transition matched. From=null, To=286


Config 16: conditions met. Proceeding with target record creation for TargetModuleId=6


[VisitorUser] Starting user creation for OrgId=262


[VisitorUser] Unexpected error for OrgId=262

MySql.Data.MySqlClient.MySqlException (0x80004005): Data too long for column 'country_code' at row 1
   at MySql.Data.MySqlClient.MySqlStream.CheckForServerError()
   at MySql.Data.MySqlClient.MySqlStream.ReadPacket()
   at MySql.Data.MySqlClient.NativeDriver.GetResult(Int32 affectedRow, Int64 insertedId)
   at MySql.Data.MySqlClient.MySqlDataReader.NextResult(CancellationToken cancellationToken)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior, CancellationToken cancellationToken)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteScalar(CancellationToken cancellationToken)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteScalar()
   at Dapper.SqlMapper.ExecuteScalarImpl[T](IDbConnection cnn, CommandDefinition& command) in C:\projects\dapper\Dapper\SqlMapper.cs:line 2855
   at Dapper.SqlMapper.ExecuteScalar(IDbConnection cnn, String sql, Object param, IDbTransaction transaction, Nullable`1 commandTimeout, Nullable`1 commandType) in C:\projects\dapper\Dapper\SqlMapper.cs:line 467
   at IncidentReporter.DAL.Repositories.UsersRepo.InsertAllTypeUser(UserDBO userDetails) in C:\GitLab-Runner\builds\27n6lYj0J\0\incident-reporter\incident-reporter-api\IncidentReporter\IncidentReporter.DAL\Repositories\UsersRepo.cs:line 799
   at OQSHA.ModuleTriggerEngine.Services.VisitorUserCreationService.CreateRecordAsync(Int32 orgId, Int32 targetModuleId, Nullable`1 targetModuleTypeId, Int32 createdByUserId, Dictionary`2 resolvedFields) in C:\GitLab-Runner\builds\27n6lYj0J\0\incident-reporter\incident-reporter-api\IncidentReporter\OQSHA.ModuleTriggerEngine\Services\VisitorUserCreationService.cs:line 150


Sending trigger callback to https://api-qa-staging-2.oqsha.com/Organisations/262/VisitorManagement/TriggerCallback for ExecutionLogId 516, TargetRecordId null, Status failed


Callback to https://api-qa-staging-2.oqsha.com/Organisations/262/VisitorManagement/TriggerCallback failed with status code Unauthorized. Error body:


Config 16: execution completed. TargetRecordId=null, Status=failed


Completed processing trigger event for message ID 181e3cdfaf6c3000


Processing trigger event for message ID 181e3d1ddbec3000: OrgId=262, SourceModuleId=121, SourceRecordId=65, Event=record_updated


Found 1 active trigger config(s) for message ID 181e3d1ddbec3000


Processing Config 16 for message ID 181e3d1ddbec3000


Config 16: no transition matched. From=286, To=296


Config 16: status transition not matched.


Sending trigger callback to https://api-qa-staging-2.oqsha.com/Organisations/262/VisitorManagement/TriggerCallback for ExecutionLogId 517, TargetRecordId null, Status skipped


Config 16: conditions not met. Logged as skipped.


Completed processing trigger event for message ID 181e3d1ddbec3000


Processing trigger event for message ID 181e3d5c676c3000: OrgId=262, SourceModuleId=121, SourceRecordId=65, Event=record_updated


Found 1 active trigger config(s) for message ID 181e3d5c676c3000


Processing Config 16 for message ID 181e3d5c676c3000


Config 16: no transition matched. From=296, To=297


Sending trigger callback to https://api-qa-staging-2.oqsha.com/Organisations/262/VisitorManagement/TriggerCallback for ExecutionLogId 518, TargetRecordId null, Status skipped


Completed processing trigger event for message ID 181e3d5c676c3000


Processing trigger event for message ID 181e41fb542c3000: OrgId=262, SourceModuleId=121, SourceRecordId=66, Event=record_updated


Found 1 active trigger config(s) for message ID 181e41fb542c3000


Processing Config 16 for message ID 181e41fb542c3000


Config 16: transition matched. From=null, To=286


Config 16: conditions met. Proceeding with target record creation for TargetModuleId=6


[VisitorUser] Starting user creation for OrgId=262


[VisitorUser] Unexpected error for OrgId=262


Sending trigger callback to https://api-qa-staging-2.oqsha.com/Organisations/262/VisitorManagement/TriggerCallback for ExecutionLogId 519, TargetRecordId null, Status failed


Callback to https://api-qa-staging-2.oqsha.com/Organisations/262/VisitorManagement/TriggerCallback failed with status code Unauthorized. Error body:


Config 16: execution completed. TargetRecordId=null, Status=failed


Completed processing trigger event for message ID 181e41fb542c3000


Processing trigger event for message ID 181e42d36bec3000: OrgId=262, SourceModuleId=121, SourceRecordId=66, Event=record_updated


Found 1 active trigger config(s) for message ID 181e42d36bec3000


Processing Config 16 for message ID 181e42d36bec3000


Config 16: no transition matched. From=286, To=296


Config 16: status transition not matched.


Sending trigger callback to https://api-qa-staging-2.oqsha.com/Organisations/262/VisitorManagement/TriggerCallback for ExecutionLogId 520, TargetRecordId null, Status skipped


Config 16: conditions not met. Logged as skipped.


Completed processing trigger event for message ID 181e42d36bec3000


Starting Module Trigger Engine NSQ consumer


Module Trigger Engine consumer started on topic=module.trigger.engine.stg, channel=module-trigger-engine


Processing trigger event for message ID 181e6cce88ac3000: OrgId=262, SourceModuleId=121, SourceRecordId=67, Event=record_updated


Found 1 active trigger config(s) for message ID 181e6cce88ac3000


Processing Config 16 for message ID 181e6cce88ac3000


Config 16: transition matched. From=null, To=286


Config 16: conditions met. Proceeding with target record creation for TargetModuleId=6


[VisitorUser] Starting user creation for OrgId=262


[VisitorUser] Linked user 20800 to company 1869.


[VisitorUser] User 20800 created for OrgId=262, SiteId=841 with ACM roles [599].


[VisitorUser] Enrolled user 20800 in 1 default batch(es).


[VisitorUser] Back-fill visitor_management.visitor_user_id: visitorId=67 userId=20800 rowsAffected=1


Sending trigger callback to https://api-qa-staging-2.oqsha.com/Organisations/262/VisitorManagement/TriggerCallback for ExecutionLogId 521, TargetRecordId 20800, Status success


Callback to https://api-qa-staging-2.oqsha.com/Organisations/262/VisitorManagement/TriggerCallback succeeded.


Config 16: execution completed. TargetRecordId=20800, Status=success


Completed processing trigger event for message ID 181e6cce88ac3000


Processing trigger event for message ID 181e718dfdac3000: OrgId=262, SourceModuleId=121, SourceRecordId=67, Event=record_updated


Found 1 active trigger config(s) for message ID 181e718dfdac3000


Processing Config 16 for message ID 181e718dfdac3000


Config 16: already executed for SourceRecordId=67. Skipping.


Completed processing trigger event for message ID 181e718dfdac3000


Starting Module Trigger Engine NSQ consumer


Module Trigger Engine consumer started on topic=module.trigger.engine.stg, channel=module-trigger-engine


Processing trigger event for message ID 181e73f7abac3000: OrgId=262, SourceModuleId=121, SourceRecordId=68, Event=record_updated


Found 1 active trigger config(s) for message ID 181e73f7abac3000


Processing Config 16 for message ID 181e73f7abac3000


Config 16: transition matched. From=null, To=286


Config 16: conditions met. Proceeding with target record creation for TargetModuleId=6


[VisitorUser] Starting user creation for OrgId=262


[VisitorUser] Linked user 20801 to company 1869.


[VisitorUser] User 20801 created for OrgId=262, SiteId=841 with ACM roles [599].


[VisitorUser] Enrolled user 20801 in 1 default batch(es).


[VisitorUser] Back-fill visitor_management.visitor_user_id: visitorId=68 userId=20801 rowsAffected=1


Sending trigger callback to https://api-qa-staging-2.oqsha.com/Organisations/262/VisitorManagement/TriggerCallback for ExecutionLogId 522, TargetRecordId 20801, Status success


Callback to https://api-qa-staging-2.oqsha.com/Organisations/262/VisitorManagement/TriggerCallback succeeded.


Config 16: execution completed. TargetRecordId=20801, Status=success


Completed processing trigger event for message ID 181e73f7abac3000


Processing trigger event for message ID 181e753d226c3000: OrgId=262, SourceModuleId=121, SourceRecordId=69, Event=record_updated


Found 1 active trigger config(s) for message ID 181e753d226c3000


Processing Config 17 for message ID 181e753d226c3000


Config 17: no transition matched. From=null, To=287


Config 17: status transition not matched.


Sending trigger callback to https://api-qa-staging-2.oqsha.com/Organisations/262/VisitorManagement/TriggerCallback for ExecutionLogId 523, TargetRecordId null, Status skipped


Config 17: conditions not met. Logged as skipped.


Completed processing trigger event for message ID 181e753d226c3000


Processing trigger event for message ID 181e7541d46c3000: OrgId=262, SourceModuleId=121, SourceRecordId=69, Event=record_updated


Found 1 active trigger config(s) for message ID 181e7541d46c3000


Processing Config 17 for message ID 181e7541d46c3000


Config 17: transition matched. From=287, To=286


Config 17: conditions met. Proceeding with target record creation for TargetModuleId=6


[VisitorUser] Starting user creation for OrgId=262


[VisitorUser] Linked user 20802 to company 1869.


[VisitorUser] User 20802 created for OrgId=262, SiteId=881 with ACM roles [599].


[VisitorUser] Enrolled user 20802 in 1 default batch(es).


[VisitorUser] Back-fill visitor_management.visitor_user_id: visitorId=69 userId=20802 rowsAffected=1


Sending trigger callback to https://api-qa-staging-2.oqsha.com/Organisations/262/VisitorManagement/TriggerCallback for ExecutionLogId 524, TargetRecordId 20802, Status success


Callback to https://api-qa-staging-2.oqsha.com/Organisations/262/VisitorManagement/TriggerCallback succeeded.


Config 17: execution completed. TargetRecordId=20802, Status=success


Completed processing trigger event for message ID 181e7541d46c3000


Processing trigger event for message ID 181e7577c6ec3000: OrgId=262, SourceModuleId=121, SourceRecordId=68, Event=record_updated


Found 1 active trigger config(s) for message ID 181e7577c6ec3000


Processing Config 16 for message ID 181e7577c6ec3000


Config 16: already executed for SourceRecordId=68. Skipping.


Completed processing trigger event for message ID 181e7577c6ec3000


Processing trigger event for message ID 181e7624ba2c3000: OrgId=262, SourceModuleId=121, SourceRecordId=68, Event=record_updated


Found 1 active trigger config(s) for message ID 181e7624ba2c3000


Processing Config 16 for message ID 181e7624ba2c3000


Completed processing trigger event for message ID 181e7624ba2c3000


Processing trigger event for message ID 181e783ddc6c3000: OrgId=262, SourceModuleId=121, SourceRecordId=70, Event=record_updated


Found 1 active trigger config(s) for message ID 181e783ddc6c3000


Processing Config 16 for message ID 181e783ddc6c3000


Config 16: transition matched. From=null, To=286


Config 16: conditions met. Proceeding with target record creation for TargetModuleId=6


[VisitorUser] Starting user creation for OrgId=262


[VisitorUser] Linked user 20803 to company 1869.


[VisitorUser] User 20803 created for OrgId=262, SiteId=841 with ACM roles [599].


[VisitorUser] Enrolled user 20803 in 1 default batch(es).


[VisitorUser] Back-fill visitor_management.visitor_user_id: visitorId=70 userId=20803 rowsAffected=1


Sending trigger callback to https://api-qa-staging-2.oqsha.com/Organisations/262/VisitorManagement/TriggerCallback for ExecutionLogId 525, TargetRecordId 20803, Status success


Callback to https://api-qa-staging-2.oqsha.com/Organisations/262/VisitorManagement/TriggerCallback succeeded.


Config 16: execution completed. TargetRecordId=20803, Status=success


Completed processing trigger event for message ID 181e783ddc6c3000


Processing trigger event for message ID 181e7b7f1cec3000: OrgId=262, SourceModuleId=121, SourceRecordId=71, Event=record_updated


Found 1 active trigger config(s) for message ID 181e7b7f1cec3000


Processing Config 16 for message ID 181e7b7f1cec3000


[VisitorUser] Linked user 20804 to company 1869.


[VisitorUser] User 20804 created for OrgId=262, SiteId=881 with ACM roles [599].


[VisitorUser] Enrolled user 20804 in 1 default batch(es).


[VisitorUser] Back-fill visitor_management.visitor_user_id: visitorId=71 userId=20804 rowsAffected=1


Sending trigger callback to https://api-qa-staging-2.oqsha.com/Organisations/262/VisitorManagement/TriggerCallback for ExecutionLogId 526, TargetRecordId 20804, Status success


Config 16: execution completed. TargetRecordId=20804, Status=success


Completed processing trigger event for message ID 181e7b7f1cec3000


Processing trigger event for message ID 181e7cf3a56c3000: OrgId=262, SourceModuleId=121, SourceRecordId=72, Event=record_updated


Found 1 active trigger config(s) for message ID 181e7cf3a56c3000


Processing Config 16 for message ID 181e7cf3a56c3000


Config 16: transition matched. From=null, To=286


Config 16: conditions met. Proceeding with target record creation for TargetModuleId=6


[VisitorUser] Starting user creation for OrgId=262


[VisitorUser] Linked user 20805 to company 1869.


[VisitorUser] User 20805 created for OrgId=262, SiteId=881 with ACM roles [599].


[VisitorUser] Enrolled user 20805 in 1 default batch(es).


[VisitorUser] Back-fill visitor_management.visitor_user_id: visitorId=72 userId=20805 rowsAffected=1


Sending trigger callback to https://api-qa-staging-2.oqsha.com/Organisations/262/VisitorManagement/TriggerCallback for ExecutionLogId 527, TargetRecordId 20805, Status success


Callback to https://api-qa-staging-2.oqsha.com/Organisations/262/VisitorManagement/TriggerCallback succeeded.


Config 16: execution completed. TargetRecordId=20805, Status=success


Completed processing trigger event for message ID 181e7cf3a56c3000


Starting Module Trigger Engine NSQ consumer


Module Trigger Engine consumer started on topic=module.trigger.engine.stg, channel=module-trigger-engine