Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
civirules
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 40
    • Issues 40
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 4
    • Merge Requests 4
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Extensions
  • civirules
  • Issues
  • #15

Closed
Open
Opened Aug 19, 2018 by Pradeep Nayak@pradeepReporter

Civirules api action exception: Unable to remove/add tags.

IPN callbacks failed silently because of CiviRules. The site has a rule that tries to add and remove a contact from a tag when a membership status is changed. In a simple use case it does work when a contact is already has tag for action as remove or not present in tag when action is add to tag. Otherwise it fails silently making transaction rollback.

Here are some logs we found when a membership was changed

Aug 20 03:25:09  [info] Civirules api action exception: Unable to remove tags. API call: EntityTag.delete with params: tag_id="1", entity_id="37", entity_table="civicrm_contact"

Aug 20 03:31:12  [info] Civirules api action exception: Unable to remove tags. API call: EntityTag.delete with params: tag_id="1", entity_id="37", entity_table="civicrm_contact"

Aug 20 03:31:56  [info] Civirules api action exception: Unable to add tags. API call: EntityTag.create with params: tag_id="2", entity_id="37", entity_table="civicrm_contact"

I have submitted a PR for this fix which actually first checks if a contact is already tagged or not if so proceed or skip depends on the action.

I am not sure if this should be handled in Core api for Entity Tag or Core expects extension to handle this.

Edited Aug 19, 2018 by Pradeep Nayak
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: extensions/civirules#15