Webhook/API Error: Action is missing

Iโ€™m getting an error when trying to run a relatively simple webhook, the error is below:

Action Details
Email Details
REST API:
{
โ€œActionโ€: โ€œโ€˜Actionโ€™ is missing.โ€,
โ€œPropertiesโ€: {},
โ€œRowsโ€:
}

Properties:
{
โ€œRestAPIVersionโ€: 2,
โ€œTableNameโ€: โ€œActivitiesโ€,
โ€œAppTemplateVersionโ€: โ€œ1.000195โ€,
โ€œAppTemplateNameโ€: โ€œ8965f1b4-7baf-49d6-b32f-eace1641b8e7โ€,
โ€œOperationโ€: โ€œREST API invokeโ€,
โ€œRecordTypeโ€: โ€œStartโ€,
โ€œResultโ€: โ€œFailureโ€
}

The template for the webhook is:

{
โ€œActionโ€: โ€œAddโ€,
โ€œPropertiesโ€: {
โ€œLocaleโ€: โ€œen-USโ€,
โ€œTimezoneโ€: โ€œCentral Standard Timeโ€,
โ€œRunAsUserEmailโ€: โ€œ<<useremail()>>โ€,
โ€œUsersettingsโ€: {
โ€œPayroll Periodโ€: โ€œ<<usersettings(Payroll Period)>>โ€,
โ€œJobsiteโ€: โ€œ<<usersettings(jobsite)>>โ€
}
},
โ€œRowsโ€: [
<<start: [related employees]>>
{
โ€œRefKeyโ€: โ€œ<<index(select(Timesheet[uniqueid],and([_thisrow-1].[refkey]=[reftimecard],[Employee Name]=[_thisrow-1].[Original])),1)>>โ€,
โ€œTimecardRefโ€: โ€œ<<[_thisrow-1].[refkey]>>โ€,
โ€œDateโ€: โ€œ<<[_thisrow-1].[date]>>โ€,
โ€œPhase Typeโ€: โ€œ<<[_thisrow-1].[Phase Type]>>โ€,
โ€œPhase Descriptionโ€: โ€œ<<[_thisrow-1].[Phase]>>โ€,
โ€œIssuesโ€: โ€œ<<[_thisrow-1].[Comments]>>โ€,
โ€œFacilityโ€: โ€œ<<[_thisrow-1].[Facility]>>โ€,
โ€œLayerโ€: โ€œ<<[_thisrow-1].[Insulation Layer]>>โ€,
โ€œStraight Timeโ€: โ€œ<<[_thisrow-1].[Straight Time]>>โ€,
โ€œOvertimeโ€: โ€œ<<[_thisrow-1].[Overtime]>>โ€,
โ€œDouble Timeโ€: โ€œ<<[_thisrow-1].[Double Time]>>โ€,
โ€œSchedule Activityโ€: โ€œ<<[_thisrow-1].[Schedule Activity]>>โ€,
โ€œSpecific Status Rowโ€: โ€œ<<[_thisrow-1].[Specific Status Row]>>โ€
}
<>
]
}

The workflow is:

Has anyone run across an error like this or have any thoughts? It seems like a straightforward process and I feel like Iโ€™m missing something obvious or have run across a bug. This error occurs when using the traditional workflow process and the new automation process.

Solved Solved
0 4 543
1 ACCEPTED SOLUTION

Update: This is a confirmed internal bug and the fix is to be deployed to production today per @Lusha_Wang

View solution in original post

4 REPLIES 4

Update: This is a confirmed internal bug and the fix is to be deployed to production today per @Lusha_Wang

@CJ_QREW is this simular to our issue?

Negative, I havenโ€™t encountered this bug. @Douglas_English

Any updates?

Top Labels in this Space