Troubleshooting SaaS Bulk Publish Issues

On this page

Checklist

A single publish must work for the target application or questionnaire.

  1. The calculated field created for the JSON body must have the correct field mappings.

  2. The formula for the calculated field must match the example in Publishing Records in Bulk Using a Data Feed (Task 2, Step 1).

  3. The records created must be visible in the report created.

  4. The XML file created must match the one in Publishing Records in Bulk Using a Data Feed (Task 5). No additional tags need to be created.

  5. The Custom Parameter keys are case sensitive. They must be similar to what is in Publishing Records in Bulk Using a Data Feed (Task 6).

  6. The Archer username details provided in the Custom Parameters section are case sensitive. The username must be identical to the one created in the Manage Users page.

  7. For non-windows authentication, the longbowUrl provided in the Custom Parameters section must begin with a Slash (/).

    For example: /engage/api/questionnaire/Publish

    For Windows Integrated SSO, the longbowUrl value is:

    https://{Engage Agent Hostname}:5001/api/v1/questionnaire/publish

    where {Engage Agent Hostname} is the is the fully qualified hostname of the web server.

    The job engine server should be able to communicate with the Engage Agent server and it's outbound port 5001 should be open.

  8. Based on the environment, the custom parameter verifyCerts must be set to . This key sets to true by default.

  9. In the Data Map, both the jsonBody and the trackingID must be mapped correctly.

  10. Set archerSSOEnabled according to the users environment. For Windows Authentication, use this variable with the value true and modify the longbow URL as detailed in Publishing Records in Bulk Using a Data Feed (Task 6).

  11. If the customer is using Windows authentication, Signed_BulkPublish_1.0.6.js is supported. For non-windows authentication, Signed_BulkPublish_1.0.4.js or later are supported.

  12. Ensure the report refresh rate is set to minimum, so it gets refreshed before the next data feed execution.

  13. Ensure the calculated JSON body field is calculated before publish using a data feed.

Bulk Publish stops after running for 6 hours

Error Resolution

Bulk Publish publishes record successfully but stops after running for 6 hours.

This is an expected behavior.

This is how any data feed works and is not configurable. If there is a data feed which needs to run for more than 6 hours, either it must be rerun manually or will be executed in the next schedule.

Bulk Publish stopped publishing after a few successful publishes

Error Resolution

Bulk Publish feed published few records successfully and then stopped publishing.

Check the data feed user session timeout. If the timeout is less than what you expect the feed to run, it will stop executing after the users session times out.

Note: Run the data feed for 6 hours which is the maximum duration any data feed can run.

Bulk Publish shows “in running state” but nothing is published

Error Resolution

Bulk Publish shows “in running state” but nothing gets published and there are no logs in the Engage Agent.

If you are using Windows Integrated Authentication SSO for Archer, use Signed_BulkPublish_1.0.6.js or later versions.

Bulk Publish is stuck

Error Resolution

Bulk Publish is stuck after a few successful published records.

This means your configuration is correct. The load on the job engine in a SaaS or hosted setup causes it to take time to publish the next set of records.

Bulk Publish runs without publishing records

Error Resolution

Bulk Publish continues to run without publishing records and times out after 6 hours.

Isolate where the issue occurs.

  1. First validate all the configurations mentioned in the check list.

  2. Check the agent logs to verify if the calls are reaching the Engage Agent.