Inbound email action creating unexpected AWA work itemsIssue Having set up an Inbound Email Action to create an incident for a particular subject/sender/etc. you are finding that work items are being generated for the record when the service channel eligibility shouldn't allow it (for example the assignment group doesn't match). SymptomsLooking at the generated incident record it's not clear why AWA would be picking up the incident for assignment.ReleaseWashington, XanaduCauseThe root cause of the problem could be the use of 'current.insert()' within the email action script. This results in the record being created before the field actions in the inbound action are applied. If there are assignment rules that are set to trigger on empty values of new records (ie. the assignment group) this will result in them being triggered and potentially starting the AWA assignment process.ResolutionEither: a) Remove the call for current.insert() in the Inbound Email Action script. b) Apply the field values that would otherwise be set by the field actions in the script instead.