# "Argument "content" is null" when pushing groups

**URL:** <https://devforum.okta.com/t/argument-content-is-null-when-pushing-groups/20004>\
**Category:** SCIM\
**Created:** [March 28, 2022, 11:52pm UTC](https://devforum.okta.com/t/argument-content-is-null-when-pushing-groups/20004 "2022-03-28T23:52:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![eheinlein](https://avatars.discourse-cdn.com/v4/letter/e/49beb7/32.png) [@eheinlein](https://devforum.okta.com/u/eheinlein)\
**Post date:** [March 28, 2022, 11:52pm UTC](https://devforum.okta.com/t/argument-content-is-null-when-pushing-groups/20004/1 "2022-03-28T23:52:32Z")

</div>

I am implementing SCIM provisioning to push users and groups from my Okta dev instance into my application. When I try to push the group via the admin console, I get the error:

> Unable to update Group Push mapping target App group The Expanse: Error while updating user group membership for group The-Expanse: argument “content” is null

I can’t tell what “content” is in this context.

Logging the request I can see that this is the POST that is coming into my app from Okta:

```auto
{
  "schemas": [
    "urn:ietf:params:scim:schemas:core:2.0:Group"
  ],
  "displayName": "The Expanse",
  "members": [
    {
      "value": "1035",
      "display": "eheinlein+ab@mydomain.com"
    },
    {
      "value": "1034",
      "display": "eheinlein+jh@mydomain.com"
    },
    {
      "value": "1036",
      "display": "eheinlein+ca@mydomain.com"
    },
    {
      "value": "1038",
      "display": "eheinlein+nn@mydomain.com"
    },
    {
      "value": "1037",
      "display": "eheinlein+ak@mydomain.com"
    }
  ]
}

```

I can confirm that the group is successfully created, and my app returns a `201 Created` with a Group body (which does include the group ID):

```auto
{
    "displayName": "The-Expanse",
    "schemas": [
        "urn:ietf:params:scim:schemas:core:2.0:Group"
    ],
    "members": [
        {
            "display": "James Holden",
            "value": "1034",
            "$ref": "/scim/v2/Users/1034"
        },
        {
            "display": "Amos Burton",
            "value": "1035",
            "$ref": "/scim/v2/Users/1035"
        },
        {
            "display": "Chrisjen Avasarala",
            "value": "1036",
            "$ref": "/scim/v2/Users/1036"
        },
        {
            "display": "Alex Kamal",
            "value": "1037",
            "$ref": "/scim/v2/Users/1037"
        },
        {
            "display": "Naomi Nagata",
            "value": "1038",
            "$ref": "/scim/v2/Users/1038"
        }
    ],
    "id": "a8287417-3e1f-486f-879f-38ad821d23b1"
}

```

What is the “content” argument that the error message is referring to?

---

<div class="post-metadata">

**Author:** ![eheinlein](https://avatars.discourse-cdn.com/v4/letter/e/49beb7/32.png) [@eheinlein](https://devforum.okta.com/u/eheinlein)\
**Post date:** [April 1, 2022, 8:51pm UTC](https://devforum.okta.com/t/argument-content-is-null-when-pushing-groups/20004/2 "2022-04-01T20:51:02Z")

</div>

Update: figured it out! The issue wasn’t with the POST to create the group, but with the follow up GET to get the group by an ID. I had introduced a bug on my side that caused the group to not be returned. Fixing that bug resolved the group sync.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/oktadev/original/1X/589c4c5f80de422d01f47cee7185a7fb8227835c.png) [@system](https://devforum.okta.com/u/system)\
**Post date:** [April 2, 2022, 8:51pm UTC](https://devforum.okta.com/t/argument-content-is-null-when-pushing-groups/20004/3 "2022-04-02T20:51:55Z")

</div>

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.