ÃÛ¶¹ÊÓƵ

Documentation

Change in rtEvent#PushEvents error handling in ÃÛ¶¹ÊÓƵ Campaign V8

Last update: Wed Jul 09 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

In ÃÛ¶¹ÊÓƵ Campaign V8, the rtEvent#PushEvents method no longer returns an error when receiving invalid payloads, such as out-of-range values for the wishedChannel field. Instead, it stores incorrect data in the RT database, causing synchronization errors in workflows like mcExec. To fix this, validate payloads before sending, correct invalid RT records, skip faulty events during sync, and monitor workflows for recurring issues.

Description description

Environment

  • Product: ÃÛ¶¹ÊÓƵ Campaign Classic Hosted
  • Version: V8 (Server Build 8.6.2, Console Build 8.6.2)
  • Instance: Stage

Issue/Symptom

  • In ÃÛ¶¹ÊÓƵ Campaign V7, the rtEvent#PushEvents method returned an error when the payload included invalid data (for example, an out-of-range value for the wishedChannelÌý´Ú¾±±ð±ô»å).

  • In ÃÛ¶¹ÊÓƵ Campaign V8, this behavior has changed:

    • The SOAP call doesn’t return an error or a success response.
    • The system stores invalid data in the RT instance database.
    • Synchronization workflows, such as mcExec, on connected marketing instances fail due to the invalid data.

Example:

  • A payload with wishedChannel="999" exceeds the 8-bit integer limit. The system stores a wrap-around value (231) without raising an error.

  • This causes synchronization errors like:

    BAS-010043 Value ‘231’ is off limits for a number of type ‘integer (8 bit)’ (range is between -128 and 127).

Resolution resolution

To prevent issues caused by invalid payloads being processed without proper error handling, follow these best practices:

  1. Make sure the data sent to the rtEvent#PushEventsmethod matches the expected types and value ranges.

    • For example, confirm that fields like wishedChannel fall within valid limits (for example, -128 to 127 for an 8-bit integer).

  2. If invalid data has already been ingested:

    • Manually correct affected records in the RT database before running synchronization workflows.
    • Alternatively, skip synchronization for events that contain invalid data.

  3. Monitor synchronization workflows such as mcExec for recurring errors caused by invalid payloads.

  4. Stay informed about future ÃÛ¶¹ÊÓƵ Campaign V8 updates that may address this behavior.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f